fix:DDC meta service health aggregation#500
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
kubectl get ddccan still show cluster health asgreenafter one MetaService pod is down. The DDC cluster health aggregation currently only considers FE availability and compute group availability, so MetaService degradation is not reflected instatus.clusterHealth.health.There is also a stale status path: once MetaService
PhasebecomesReady,UpdateComponentStatusdoes not downgrade it when the available MetaService replicas drop below the desired replicas.Changes
PhasetoReconcilingwhen not all desired MetaService replicas are ready on the latest StatefulSet revision.redyellowTests