-
Notifications
You must be signed in to change notification settings - Fork 612
MultiKueue: prevent a hung remote watch from stopping all-cluster admission #11207
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
Merged
k8s-ci-robot
merged 4 commits into
kubernetes-sigs:main
from
trilamsr:fix/multikueue-watch-establish-timeout
May 18, 2026
+156
−4
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
Exploratory question to confirm my understanding: could this issue be also mitigated by increasing the
GroupKindConcurrencylevel for MultiKueueCluster for the controller, wdyt? Code pointer to the configuration: https://github.com/kubernetes-sigs/kueue/blob/main/apis/config/v1beta2/configuration_types.go#L264C2-L264C22In that case when one Reconcile is stuck the other may continue
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.
I don't think it actually buys us anything in this code path. The knob is wired through correctly (the controller doesn't override
MaxConcurrentReconciles), so in principle you'd get N parallel workers. But Reconcile callssetRemoteClientConfig, which grabsclustersReconciler.lock(a single controller wide write mutex atmultikueuecluster.go:394) and holds it through the entiresetConfig→establishWatch→c.Watch()chain. So when one worker is parked insidec.Watch(), every other Reconcile that wants to do anything with a different cluster sits waiting on that same lock.In practice concurrency=N collapses back to 1 whenever any remote is hung. Bumping the knob would only help after we also split that lock per cluster, or released it before establishing the watch. Probably a separate PR. Happy to file a follow up issue for it if you want.
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.
I see, thank you for the summary, I now understand why this would not work currently, and why fixing the problem is not straighforward.
Having said that, I think this renders
GroupKindConcurrencyuseless forMultiKueueClusterdue to very technical reasons which can be considered a bug by a user.So, please file an issue for that. Feel free to work on it, or just keep it posted for some contributors.
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.
Filed #11297 to track the lock refactor. Leaving it unassigned for now so it's open for any contributor to pick up.