Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support multi-level locality aware routing #1796

Closed
htuch opened this issue Oct 2, 2017 · 3 comments
Closed

Support multi-level locality aware routing #1796

htuch opened this issue Oct 2, 2017 · 3 comments
Labels
api/v4 Major version release @ end of Q3 2020 help wanted Needs help!

Comments

@htuch
Copy link
Member

htuch commented Oct 2, 2017

Now that Envoy is aware of hierarchical locality (region, zone, sub_zone), it may be useful to be able to perform LB in a region, zone and sub_zone aware fashion. The current implementation groups these into a single flat locality identifier, so is effectively concatenating the locality names across levels.
@htuch htuch added api/v2 help wanted Needs help! labels Oct 2, 2017
htuch added a commit to htuch/envoy that referenced this issue Oct 2, 2017
@htuch
upstream: switch zone-aware routing to single level locality-aware.
796d7f5 
We now do single level locality-aware routing, using the EDS supplied Locality consisting of
(region, zone, sub_zone). This is only a simple extension and rename of zone aware routing, there is
no support yet for multi-level locality routing (see envoyproxy#1796).

Signed-off-by: Harvey Tuch <[email protected]>
@htuch htuch mentioned this issue Oct 2, 2017
Merged
htuch added a commit that referenced this issue Oct 3, 2017
@htuch
upstream: switch zone-aware routing to single level locality-aware. (#…
550a8d9 
…1797)

We now do single level locality-aware routing, using the EDS supplied Locality consisting of
(region, zone, sub_zone). This is only a simple extension and rename of zone aware routing, there is
no support yet for multi-level locality routing (see #1796).

Signed-off-by: Harvey Tuch [email protected]
rshriram pushed a commit to rshriram/envoy that referenced this issue Oct 30, 2018
@istio-testing
release-binary: add missing dash to checksum filename (envoyproxy#1796)
84b71b8
@derekargueta derekargueta mentioned this issue Mar 20, 2019
Open
@htuch htuch added api/v4 Major version release @ end of Q3 2020 and removed api/v2 labels Aug 29, 2019
@htuch
Copy link
Member Author

htuch commented Aug 29, 2019

@rshriram @mattklein123 is there a final direction we decided on taking on this? In any case, I don't see any major changes around this until v4.

@mattklein123
Copy link
Member

@htuch I haven't thought about this in a while. TBH I think we should just close this until someone asks for it explicitly but up to you.

@htuch
Copy link
Member Author

htuch commented Sep 3, 2019

Ack, closing it out for now, will reopen if anyone wants this.

@htuch htuch closed this as completed Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api/v4 Major version release @ end of Q3 2020 help wanted Needs help!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mattklein123 @htuch