Support for serially using multiple connections in steady state replication

XMLWordPrintableJSON

    • Service Arch
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Using a single persistent connection for steady state replication could be a problem if the volume of traffic is very high and the socket used is transiting a WAN with limited bandwidth (that's also used for other critical traffic).

      Providing an option which forced some kind of round robin-ing, or even just dropping the connection occasionally, would ensure that we balance that traffic across unique 5 tuples, which would ensure we don't oversubscribed any one particular path.

              Assignee:
              [DO NOT USE] Backlog - Service Architecture
              Reporter:
              Mira Carey
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: