-
Notifications
You must be signed in to change notification settings - Fork 4.6k
endpointsharding: Allow children to remain idle if configured #8031
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
arjan-bal
merged 4 commits into
grpc:master
from
arjan-bal:endpointsharding-configure-auto-reconnect
Jan 28, 2025
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
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.
Because we're calling into the child from a goroutine here:
bw.es.childMuto avoid concurrent calls in,Close()needs it (and also needed it before you added the method explicitly here, so good that we caught it), andBalancer, since directly calling it is wrong.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.
Before this PR, calls to
balancerWrapper.Close()and updates toendpointsharding.closedwere holdinges.ChildMu:In
endpointshardng.Close():grpc-go/balancer/endpointsharding/endpointsharding.go
Line 187 in 9d4fa67
In
endpointshardng.UpdateClientConnState():grpc-go/balancer/endpointsharding/endpointsharding.go
Lines 104 to 105 in 9d4fa67
grpc-go/balancer/endpointsharding/endpointsharding.go
Lines 150 to 157 in 9d4fa67
Maybe I'm not understanding this point correctly?
I've removed the embedded balancer.Balancer from
balancerWrapperand provided methods namedupdateClientConnStateLockedandcloseLockedand that expect the caller to lockes.ChildMu.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.
Oh, I see... I missed where it grabbed the lock in
Closeand thought it was just delegating directly to the wrappers.This now seems good and makes it explicit what is required.