Skip to content

Change DatabaseNodeService error logs to warnings#138438

Merged
masseyke merged 3 commits intoelastic:mainfrom
masseyke:reduce-geoip-downloader-log-level
Nov 24, 2025
Merged

Change DatabaseNodeService error logs to warnings#138438
masseyke merged 3 commits intoelastic:mainfrom
masseyke:reduce-geoip-downloader-log-level

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 :Distributed/Ingest Node Execution or management of Ingest Pipelines 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 (obsolete) DO NOT USE. This team no longer exists. 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

@masseyke masseyke added auto-backport Automatically create backport pull requests when merged v9.2.2 v8.19.8 v9.1.8 labels Nov 24, 2025
@masseyke masseyke merged commit 44e43ce into elastic:main Nov 24, 2025
35 of 36 checks passed
@masseyke masseyke deleted the reduce-geoip-downloader-log-level branch November 24, 2025 15:50
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
9.2
8.19 Commit could not be cherrypicked due to conflicts
9.1 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 138438

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

Labels

auto-backport Automatically create backport pull requests when merged backport pending >bug :Distributed/Ingest Node Execution or management of Ingest Pipelines Team:Data Management (obsolete) DO NOT USE. This team no longer exists. v9.2.2 v9.3.0

3 participants