Details
-
Epic
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
None
Description
Haven't scoped it yet but expect there to be Drivers changes.
Description of Linked Ticket
Summary
Allow a client to receive a response for a request from a node different than the one it made the request to
Motivation
Sometimes we route requests to nodes that can't service those requests. Today all we can do would be to either fail those requests (and retarget + retry) or make another request from the initial node, routing the response back through that node to the client. Both of those approaches require an extra network hop that isn't strictly speaking necessary.
By routing a response directly from the initial node to the node which can service the request, a client could receive a misrouted request in 3 hops, rather than 4.
(Proposed) Client -> ineligible node -> eligible node -> client
vs.
(fail + retarget) Client -> ineligible node -> Client -> eligible node -> Client
vs.
(route request) Client -> ineligible node -> eligible node -> ineligible node -> Client
Cast of Characters
- Product Owner:
- Project Lead:
- Program Manager: