Details
-
Task
-
Resolution: Won't Do
-
Major - P3
-
3.6
-
None
Description
Description
I believe the implementation for SERVER-26848 sets settings.catchUpTimeoutMillis to be infinite (-1) by default.
In pre-3.6, the value cannot be a negative number, thus it was defaulted to either 2000 or 60000.
The 4.0 upgrade notes mentions this setting to be increased to mitigate w:1 rollbacks.
However, the 3.6 upgrade notes does not mention this setting at all. Therefore, customers upgrading from pre-3.6 to 3.6 will tend to have the 2000 or 60000 default values.