Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
Fully Compatible
-
ALL
-
v3.4
-
Repl 2017-06-19, Repl 2017-07-10
-
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.