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.

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

M:N zone aware routing #6333

Open
derekargueta opened this issue Mar 20, 2019 · 4 comments
Open

M:N zone aware routing #6333

derekargueta opened this issue Mar 20, 2019 · 4 comments
Labels
enhancement Feature requests. Not bugs or questions. help wanted Needs help!

Comments

@derekargueta
Copy link
Member

Title: M:N zone aware routing

Description:
Currently zone aware routing is only supported if there are equal numbers of zones for both the client and server per the documentation. It'd improve flexibility if zone aware routing can occur between M client zones and N server zones, such as if a particular service fails in one zone, the client could still try to optimize routing locally.

This seems orthogonal to #1796.

@mattklein123 mattklein123 added the enhancement Feature requests. Not bugs or questions. label Mar 20, 2019
@mattklein123
Copy link
Member

@derekargueta agreed it would be nice to have this work if someone wants to do the extra algorithm work.

@derekargueta
Copy link
Member Author

@mattklein123 we have an internal implementation in Finagle that is quite similar to Envoy's, with additional handling for the cases where the number of zones mismatch.

@fishcakez @jparise thoughts on creating a publicly available version of the design and providing an implementation to Envoy?

cc @rgs1

@mattklein123
Copy link
Member

@derekargueta FWIW I doubt this would be difficult to implement in Envoy, even without any example code open sourced. I think the math is pretty straightforward. Someone just needs to work on it. (Working code would be nice also though!)

@derekargueta
Copy link
Member Author

It's not yet clear if we can provide code. Agreed it's fairly straightforward, but since I'm well-versed in our internal implementation I think I'll pass on pursuing this as a precaution, so for now consider this an open invitation for a volunteer 🙂

We are looking at helping out with #5598

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature requests. Not bugs or questions. help wanted Needs help!
Projects
None yet
Development

No branches or pull requests

2 participants