-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
balancer/pickfirstleaf: Fix handling of Addresses with Metadata #8227
base: master
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8227 +/- ##
==========================================
- Coverage 82.16% 82.03% -0.13%
==========================================
Files 410 411 +1
Lines 40248 40284 +36
==========================================
- Hits 33068 33047 -21
- Misses 5830 5875 +45
- Partials 1350 1362 +12
🚀 New features to boost your workflow:
|
b5b2dbc
to
c8fb55c
Compare
Do we still want to do this? The most recent comment on etcd-io/etcd#19700 (comment) says that etcd itself is not affected by this and that they are going to prioritize the long term fix of not using the But I also see that your note saying |
Waiting to discuss this with @dfawley. If we think is fine not to support Metadata to differentiate addresses in the new pickfirst, we would need to change the following condition. Having a test for the behaviour would be good. grpc-go/balancer/pickfirst/pickfirstleaf/pickfirstleaf.go Lines 924 to 928 in 732f3f3
|
Addresses: #8225
This PR introduces a new data structure that wraps AddressMap but considers
Address.Metadata
while comparing map keys. This is required since pickfirst must consider addresses with differentMetadata
as separate.RELEASE NOTES:
Address.Metadata
field.