internal: Fixed the cluster status cannot be changed after the POD ex… #366
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
runkecheng
force-pushed
the
fix_kill_pod_cannot_failover
branch
from
00208e2 to
c1b775a
Compare
Contributor
|
LGTM |
runkecheng
force-pushed
the
fix_kill_pod_cannot_failover
branch
from
c1b775a to
0645965
Compare
runkecheng
force-pushed
the
fix_kill_pod_cannot_failover
branch
from
0645965 to
2932c8b
Compare
zhl003
pushed a commit
to zhl003/radondb-mysql-kubernetes
that referenced
this pull request
Aug 17, 2022
…ilover internal: Fixed the cluster status cannot be changed after the POD ex…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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?
/bug
Which issue(s) this PR fixes?
Fixes #353
What this PR does?
Summary:
In K8S, when using DNS to access the POD, even if the POD does not exist, the connection can be established, so it is necessary to limit the timeout time when sending the HTTP request, otherwise it will not obtain the return result.
This is the cause of the cluster status that can't be updated after the POD fault.
by
e2eSpecial notes for your reviewer?