-
Notifications
You must be signed in to change notification settings - Fork 3.9k
xds: Support localities in multiple priorities #9683
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
Conversation
a24705b
to
e4b7195
Compare
Additional logic to support for the same locality appearing under multiple priorities.
e4b7195
to
fc7d9ab
Compare
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.
Sorry I miss the bigger picture why moving the attribute to eag level from locality would support locality in multiple priories? Setting different priority or weight for each endpoint? Brief description of background and what's next would be great!
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.
I didn't look too deeply, but this looks about right. "The shape is right." And it might actually be correct, too.
This change came out of a chat where it was realized that to be faithful with the xDS spec we need to support the same locality having different weights if it appears under more than one locality. The current code uses a single map from locality to priority so it would not work in this scenario - locality can only have one weight across all priorities. There are no next steps, just this tweak to the logic. |
Additional logic to support for the same locality appearing under multiple priorities.
Additional logic to support for the same locality appearing under multiple priorities.