-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
Repl 2019-02-11
-
50
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We write the prepare oplog entry here, but this only occurs on the primary. On a secondary, the prepareOpTime would be null.
This could be a problem on secondaries because the stableTimestamp would always move forward, causing us to possibly commit a transaction before the stableTimestamp.
- is related to
-
SERVER-38620 prepareTransaction call doesn't set _prepareOpTime if transaction was recovered
-
- Closed
-