[SERVER-4664] Adding slaveDelay on a passive secondary node stops replication to active secondary Created: 11/Jan/12  Updated: 30/Mar/12  Resolved: 19/Jan/12

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

Type: Bug Priority: Major - P3
Reporter: Anup Chatterjee Assignee: Kristina Chodorow (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-4439 Replica set members shouldn't sync fr... Closed
Operating System: ALL
Participants:

 Description   

We have a Replica set with
2 secondary nodes and 1 arbiter.
One secondary node is set with priority = 0 (passive). We are trying to add a slaveDelay on the passive node.
After adding delay to passive secondary, using rs.reconfig(). We noticed that the active secondary stops receiving oplogs from primary.
Once slaveDelay is set, it seems, both active and passive secondary stop receiving oplog/sync.


Generated at Thu Feb 08 03:06:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.