Move updating connectivity state outside of subchannel lock#2601
Merged
Conversation
81ad06f to
35edd39
Compare
|
|
||
| if (connectionRequested) | ||
| { | ||
| UpdateConnectivityState(ConnectivityState.Connecting, "Connection requested."); |
Contributor
There was a problem hiding this comment.
Is this now going to cause races where someone else comes along and modifies the Subchannel state and we end up updating it to Connecting when it should stay as TransientFailure or Ready?
Member
Author
There was a problem hiding this comment.
I believe this is fine. The logic in load balancing is designed that state can change at any point, and other parts of the system then react to it. All other places update the connectivity state outside the subchannel lock, this one is the outlier.
BrennanConroy
approved these changes
Feb 25, 2025
|
Would this be the cause of this reported issue? #2612 |
This was referenced Jul 29, 2025
Closed
Closed
This was referenced Aug 5, 2025
Closed
This was referenced May 13, 2026
Open
Open
Open
Bump the nuget-production-dependencies group with 22 updates
laurentpf5/opentelemetry-nginx-demo#346
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Fixes #2589
In connection manager and friends there are two important types of lock:
It's safe to take a subchannel lock inside the connection manager lock, but doing the opposite can lead to a deadlock.
There is one place locks were taken in the incorrect order which could cause a deadlock in rare circumstances: the channel is pick first, it has an idle subchannel, and a connection request occurs at the same time as the resolver updates.
Repoed in a unit test:
The fix is to move the connectivity state update outside of the subchannel lock.