[SERVER-42943] Support for serially using multiple connections in steady state replication Created: 20/Aug/19  Updated: 06/Dec/22  Resolved: 12/Nov/21

Status: Closed
Project: Core Server
Component/s: Networking, Replication
Affects Version/s: None
Fix Version/s: features we're not sure of

Type: New Feature Priority: Major - P3
Reporter: Mira Carey Assignee: Backlog - Service Architecture
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-44712 Add a server parameter switch to cont... Closed
Assigned Teams:
Service Arch
Participants:

 Description   

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.



 Comments   
Comment by Lauren Lewis (Inactive) [ 12/Nov/21 ]

We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:01:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.