[SERVER-47993] Make coordinateCommitTransaction return the decision once the decision has been written with the user's writeConcern Created: 06/May/20  Updated: 29/Oct/23  Resolved: 27/May/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Cheahuychou Mao
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-37364 Coordinator should return the decisio... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-05-18, Sharding 2020-06-01
Participants:

 Description   

After SERVER-37364, the decision is returned once it's majority-committed: the decision promise is emplaced after the TransactionCoordinator waits for the decision to be durable.

This ticket is to emplace the decision promise as soon as the decision is made. Since coordinateCommitTransaction always sets the Client's last OpTime to the system last OpTime before returning the decision, the Client will automatically wait for the user's writeConcern of an OpTime at or later than the decision's OpTime.



 Comments   
Comment by Githook User [ 27/May/20 ]

Author:

{'name': 'Cheahuychou Mao', 'email': 'cheahuychou.mao@mongodb.com', 'username': 'cheahuychou'}

Message: SERVER-47993 Make coordinateCommitTransaction return the decision once the decision has been written with the user's writeConcern
Branch: master
https://github.com/mongodb/mongo/commit/f85e94d5ad4d98ea7e68af1990712a965756d883

Generated at Thu Feb 08 05:15:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.