-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication, Sharding
-
None
-
Fully Compatible
-
Repl 2019-04-08
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.
- depends on
-
SERVER-39035 Specify durable_timestamp when committing prepared transaction
- Closed