Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
Fully Compatible
-
Repl 2019-04-08
Description
Currently the cross-shard transaction coordinator chooses its commit timestamp as the maximum of the prepare timestamps plus one. Instead, it should choose the commit timestamp as the maximum of the prepare timestamps.
Attachments
Issue Links
- depends on
-
SERVER-39035 Specify durable_timestamp when committing prepared transaction
-
- Closed
-