-
Type: Improvement
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
v3.4, v3.2
-
Repl 2017-02-13, Repl 2017-03-06, Repl 2017-03-27, Repl 2017-04-17
Currently, if the i field of the global OpTime on a server increments past signed int max, we abort the process:
if (val.getInc() & 0x80000000) { mongo::warning() << "clock skew detected prev: " << val.getSecs() << " now: " << (unsigned) time(0) << std::endl; return true; }
Instead, we could handle this by incrementing the "secs" field by one and resetting the "inc" field back to 1. (The code resets the inc field back to 1 instead of 0 in the normal case, for some reason.)
- duplicates
-
SERVER-28352 Fix ticks increment in LogicalCLock::reserveTicks
- Closed