[SERVER-29383] When catchUpTimeoutMillis is 0, we should skip doing catchup entirely Created: 26/May/17  Updated: 30/Oct/23  Resolved: 28/Jun/17

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Siyuan Zhou
Resolution: Fixed Votes: 0
Labels: PM-722
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4
Sprint: Repl 2017-06-19, Repl 2017-07-10
Participants:
Linked BF Score: 0

 Description   

Currently if catchUpTimeoutMillis is 0, we enter primary catchup mode and set a timeout to fire immediately. This is unnecessary and confusing; under some conditions the system can enter primary catchup mode and actually catch up before the "immediate" timeout fires, due to locking and scheduling vagaries.



 Comments   
Comment by Githook User [ 06/Jul/17 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-29383 When catchUpTimeoutMillis is 0, we should skip doing catchup entirely

(cherry picked from commit 086b9e1430f44c89dfb54b1d32cddb75fde1a621)
Branch: v3.4
https://github.com/mongodb/mongo/commit/06cf6bbd89782656a73bfe6e591cb4730c460ead

Comment by Githook User [ 28/Jun/17 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-29383 When catchUpTimeoutMillis is 0, we should skip doing catchup entirely
Branch: master
https://github.com/mongodb/mongo/commit/086b9e1430f44c89dfb54b1d32cddb75fde1a621

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