[SERVER-34828] initial sync should not consider slave delay setting during oplog application Created: 03/May/18  Updated: 29/Oct/23  Resolved: 04/May/18

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

Type: Bug Priority: Minor - P4
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-12151 Improve slaveDelay behavior during tr... Closed
is related to SERVER-15602 Add (cppunit) test for initial sync +... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-05-07
Participants:

 Description   

A node's slaveDelay setting the replica set configuration should not affect its behavior during initial sync. The current batching logic currently takes the slaveDelay into consideration when batching operations read from the syncis that will be applied. This introduces arbitrary batch limits and is irrelevant to the final state of the initial syncing node's oplog we are trying to reach.



 Comments   
Comment by Githook User [ 04/May/18 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-34828 remove unused getSlaveDelay initial sync option
Branch: master
https://github.com/mongodb/mongo/commit/59510690f9e8779197980d9627a732145a014d98

Comment by Githook User [ 03/May/18 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-34828 initial sync ignores slave delay setting during oplog application
Branch: master
https://github.com/mongodb/mongo/commit/cf1cb92a0d1c7ca4156cc65e8af440f4a8678219

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