-
Notifications
You must be signed in to change notification settings - Fork 2
server: fix deadlock of pending_session_id_rotations mutex #189
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
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
Commit bccfc81 fixes the leaking UDP sessions. But it introduces a deadlock, by trying to lock the same Mutex twice consecutively on error condition. Luckily our parking lot deadlock detection pin pointed it out. Fixing it by locking once and using the same guard for removing stale entry.
Code coverage summary for 91eb6a8:
✅ Region coverage 54% passes |
kp-thomas-yau
approved these changes
Apr 10, 2025
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
Commit bccfc81 fixes the leaking UDP sessions. But it introduces a deadlock, by trying to lock the same Mutex twice consecutively on error condition.
Luckily our parking lot deadlock detection pin pointed it out.
Fixing it by locking once and using the same guard for removing stale entry.
Motivation and Context
Server instances are restarted frequently
How Has This Been Tested?
Verified in prod that instances are stable without deadlock
Types of changes
Checklist:
main