[client] Add another queue for re-enqueue operation only in LookupSender to avoid deadlocks during re-enqueue #2122
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
… exiting when getting a null gateway
swuferhong
force-pushed
the
fix-lookup-dead-block
branch
6 times, most recently
from
14260b7 to
32347d2
Compare
swuferhong
changed the title
…der to avoid deadlocks during re-enqueue
swuferhong
force-pushed
the
fix-lookup-dead-block
branch
from
32347d2 to
240b400
Compare
wuchong
approved these changes
Dec 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Purpose
Linked issue: close #2110
Add another queue for re-enqueue operation only in LookupSender to avoid deadlocks during re-enqueue
Brief change log
Tests
API and Format
Documentation