[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: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2020-05-18, Sharding 2020-06-01 | ||||||||
| Participants: | |||||||||
| Description |
|
After 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: |