Skip to content

Conversation

@masseyke
Copy link
Member

If we have a problem retrieving a database, we log it at error level. However, this creates a lot of noise in the logs for little value -- the problem is almost guaranteed to be in a place this class cannot control. For example, we see this class log dozens of error-level log messages when the .geoip_databases shards cannot be allocated. But that is a more serious problem that is correctly logged elsewhere. This PR reduces the level of the logs to warn so that the presense of dozens error-level logs does not distract someone who is looking for the real problem.

@masseyke masseyke added >bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP v9.3.0 labels Nov 21, 2025
@masseyke masseyke requested a review from szybia November 21, 2025 18:45
@elasticsearchmachine elasticsearchmachine added the Team:Data Management Meta label for data/management team label Nov 21, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@elasticsearchmachine
Copy link
Collaborator

Hi @masseyke, I've created a changelog YAML for you.

@@ -0,0 +1,5 @@
pr: 138438
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we backport as well?

sounds like a nice-to-have

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Team:Data Management Meta label for data/management team v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants