Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-822

Asymmetric Routing for Remote Procedure Calls

    XMLWordPrintableJSON

Details

    • Icon: Epic Epic
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None

    Description

      Downstream Change Summary

      Haven't scoped it yet but expect there to be Drivers changes.

      Description of Linked Ticket

      Epic Summary

      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:

      Documentation

      Scope Document
      Technical Design Document

      Attachments

        Activity

          People

            Unassigned Unassigned
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: