[SERVER-59340] Allow to select sync target based on staleness time in Chained Replication Created: 13/Aug/21  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Alexey Matyushin Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 2021-08-13T14-13Z - MongoDB Server Chained Replication (proposal).png    
Assigned Teams:
Replication
Participants:
Case:

 Description   

Issue,
Chained Replication is enabled by default in all supported MongoDB Server releases, and this means that a SECONDARY might select another SECONDARY as a sync target with large replication lag but very low ping time.

Metadata,

  • MongoDB Server version: v. 4.0.X, v. 4.2.X, v. 4.4.X, v. 5.0.X

What we need from this SERVER ticket,

  • Can we consider enhancing Chained Replication feature by adding ability to configure sync target based on staleness time?
    • Here is the diagram to describe the proposal,

Thanks in advance,
Alexey


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