-
Type: New Feature
-
Resolution: Won't Do
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Networking, Replication
-
None
-
Service Arch
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.
- is related to
-
SERVER-44712 Add a server parameter switch to control the use of tailable exhaust cursors for oplog fetching
- Closed