Change DatabaseNodeService error logs to warnings #138438
Open
+10
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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_databasesshards 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.