You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
@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?
@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!)
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 🙂
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.
The text was updated successfully, but these errors were encountered: