-
Notifications
You must be signed in to change notification settings - Fork 27
Fix keep-alive deadlock: wait for a signal instead of bare select {} #405
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
sumitanvekar
merged 3 commits into
ExpediaGroup:main
from
gsi85:fix/keepalive-deadlock-on-idle
Jul 30, 2026
Merged
Changes from all commits
Commits
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
Oops, something went wrong.
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.
Could you test this in a kubernetes environment and confirm the behaviour is as expected?
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.
Added
TestKeepAliveExitsGracefullyOnSigterm(1ebb539) that reproduces the pod scenario at process level: it runs the built binary with the target never becoming ready (so warm-up sends nothing and the process goes idle β the exact condition that used to deadlock), asserts the process stays up, then sendsSIGTERM(what kubelet delivers on pod termination) and asserts a clean exit (status 0). Before the fix that idle state aborts withall goroutines are asleep - deadlock!; after it, the container stays up and exits 0 onSIGTERM. Runs in ~3.5s locally and in CI.We've also already validated the behaviour on live pods in our own Kubernetes environment. Happy to go into more detail over internal channels if that would help.