[Backport 1.29] watch query timeout backport k8s-dqlite #4653
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
|
Testing multi-distros fails since after the lxd separation the community images are not available anymore. Removing Centos from run. |
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.
Description
Backports watcher query timeout in k8s-dqlite: canonical/k8s-dqlite#161
The PR adds a timeout on long running after queries in k8s-dqlite which are part of the watcher's poll loop.
The timeout is configurable using the
watch-query-timeoutflag.Context
This PR addresses issues raised in microk8s where after the leader node is removed from the cluster the remaining nodes also go into
NotReadystate for ~20 minutes. This timeout helps the responsiveness of the cluster after loosing its leader.