-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.2
-
Repl 2019-07-01
-
21
We no longer wait for write concern on the client lastOp no matter what as of SERVER-33727. We only do so if the client explicitly set the lastOp forward. Retrying prepareTransaction only sets the lastOp if it is less than the prepareOpTime. We really need to call setLastOpToSystemLastOpTime always and then also set it to the prepareOpTime if that's still greater. That will make sure prepare retries always wait for write concern.
- is related to
-
SERVER-45400 Reduce OplogFetcher getMore awaitData timeout for nodes in RollbackTest fixture
- Closed