fix(health check): check cluster status for multiple times in health check go get rid of socket connection failure #2310 #2311
Conversation
This file contains 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
|
LGTM |
pikehuang
changed the title
pikehuang
force-pushed
the
feature/enhance-cluster-healchcheck-20231024
branch
2 times, most recently
from
5d90a2c
to
622f85f
Compare
in health check to go get rid of socket connection failure tkestack#2310
pikehuang
force-pushed
the
feature/enhance-cluster-healchcheck-20231024
branch
from
622f85f
to
9731331
Compare
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.
What type of PR is this?
What this PR does / why we need it:
fix bug #2310
simple description:
cluster health check will failed in most case bacause the socket connection to the target cluster is not stable, so we check multiple times when for cluster health check.
Which issue(s) this PR fixes:
Fixes #2310
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: