-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
mds: fix liveness probe timeout #14798
mds: fix liveness probe timeout #14798
Conversation
"timeout", | ||
fmt.Sprintf("%d", mdsCmdTimeout), |
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.
timeout
can keep the script from running too long, but it exits with error code after timeout, which we don't want. To resolve, move the config for the timeout from here, to the new --connect-timeout=<mdsCmdTimeout>
in the script.
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.
lgtm
Converting to draft while I test what Travis suggested in huddle |
bd1feca
to
27207af
Compare
When the MDS liveness probe times out, it should not fail the probe. If the cluster has a network partition or other issue that causes the Ceph mon cluster to become unstable, `ceph ...` commands can hang and cause a timeout. In this case, the MDS should not be restarted so as to not cause cascading cluster disruption. Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com>
27207af
to
ad1bae9
Compare
Tested well manually in 2 different environments 👍 |
mds: fix liveness probe timeout (backport #14798)
mds: fix liveness probe timeout (backport #14798)
When the MDS liveness probe times out, it should not fail the probe. If the cluster has a network partition or other issue that causes the Ceph mon cluster to become unstable,
ceph ...
commands can hang and cause a timeout. In this case, the MDS should not be restarted so as to not cause cascading cluster disruption.Checklist: