Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Fully Compatible
-
ALL
-
v3.4
-
Repl 2017-09-11
-
0
Description
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.
Attachments
Issue Links
- is related to
-
SERVER-47695 Write commands run by threads that can survive rollback can fail operationTime invariant in ServiceEntryPoint
-
- Closed
-