[SERVER-24980] Secondary back pressure in replication Created: 11/Jul/16  Updated: 06/Dec/22  Resolved: 18/Jan/17

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

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

Assigned Teams:
Replication
Participants:

 Description   

The goal of this ticket is to put in place a mechanism that prevents secondary servers from falling off the back of the primary's oplog. A minimal solution would be to prohibit the primary from deleting entries from its oplog that have not yet replicated to a majority of voting members in the replica set.



 Comments   
Comment by Eric Milkie [ 18/Jan/17 ]

We are going to implement back pressure in the storage engine instead – its effects will solve this issue.

Generated at Thu Feb 08 04:07:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.