Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

correct where to increment the clusterNotFound count and adjust quarantine log level #950

Merged
merged 1 commit into from
Dec 7, 2023

Conversation

bohhyang
Copy link
Contributor

@bohhyang bohhyang commented Dec 6, 2023

Summary
Currently the clusterNotFound count is incremented when there is no Uris in the cluster in addition to when the cluster config is not found. This change moves it to a place which only increment for cluster config not found.

Also, changing the log level about long-quarantined hosts to Info instead of Error, because 1) often it's just a temporary small capacity which's not causing availability issue. 2) it floods the upstream app's log triggering alerts and/or creating EXC tickets that the upstream app owner is not responsible for. Clarified the log message to show the issue is the downstream host's health.

Test done
build and test

Copy link
Collaborator

@brycezhongqing brycezhongqing left a comment

Choose a reason for hiding this comment

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

LGTM

@bohhyang bohhyang merged commit e949cf1 into master Dec 7, 2023
2 checks passed
@bohhyang bohhyang deleted the bohan/clusterMetric branch December 7, 2023 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants