-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v3.4
-
Repl 2017-09-11
-
0
A write that fails may result in a call to setLastOpToSystemLastOpTime. We invariant that the last optime on a client never goes backwards, but the system optime can indeed go backwards after a rollback. If that happens we should just refuse to set the last optime on the client backwards, but we shouldn't crash.
- is related to
-
SERVER-47695 Write commands run by threads that can survive rollback can fail operationTime invariant in ServiceEntryPoint
- Closed