-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
Repl 2019-02-11
When calling prepareTransaction, _prepareOpTime isn't set when recovering a prepared transaction. As a result, we can falsely return true when checking that the commitTimestamp is strictly greater than the prepareTimestamp (which would be set to the default (0, 0)). This would be a problem for failover test suites.
- related to
-
SERVER-38866 Ensure that secondaries correctly pin the stableTimestamp when there are prepared transactions
-
- Closed
-