-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.2.0-rc2
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.2
-
Repl 2019-07-29
-
19
When reconstructing a prepared transaction during replication recovery, we try to timestamp a multikey write with a timestamp from the LogicalClock. The LogicalClock may not have been initialized yet, though, which leads to an error if we try to timestamp the write with a zero timestamp. A proposed solution is to instead propagate the prepare timestamp of the transaction into that codepath so that we can timestamp the write with the transaction's prepare timestamp.
- is related to
-
SERVER-49949 Reconstructing prepared transactions containing multi-key writes crashes the initial syncing node.
- Closed
-
SERVER-53932 Multikey write during recovery of prepared transaction could use commit timestamp < stable timestamp
- Closed
- related to
-
SERVER-48010 Substitute ghost timestamp with no-op write in multi-statement txn multikey sidetxn write
- Closed