[SERVER-39042] Choose commit timestamp for transaction as max(prepare timestamps) Created: 16/Jan/19  Updated: 29/Oct/23  Resolved: 02/Apr/19

Status: Closed
Project: Core Server
Component/s: Replication, Sharding
Affects Version/s: None
Fix Version/s: 4.1.10

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-39035 Specify durable_timestamp when commit... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-04-08
Participants:

 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.



 Comments   
Comment by Githook User [ 02/Apr/19 ]

Author:

{'email': 'pvselvan@umich.edu', 'name': 'Pavi Vetriselvan', 'username': 'pvselvan'}

Message: SERVER-39042 Coordinator does not add one to commitTimestamp
Branch: master
https://github.com/mongodb/mongo/commit/e8f8a1bf5f4a9dea142e93d82639d96073fc09a5

Generated at Thu Feb 08 04:50:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.