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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this can't be checked here as the
getHealth
call here will be retried to fallback nodes, meaning this log will only be triggered if all connected nodes are unhealthy which is not what we want as per issue.Please double check what was noted in the issue, we might have to use the url score tracked in the http client internally to determine if primary node is unhealthy, this also avoids false positives, i.e. a single failed request will not trigger an unhealthy warning.
See also related PR #6415 on how we currently track if primary node is unhealthy in metrics.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understood how to solve it , thanks for the info , will be back with the fix .