[SERVER-35764] Add 'coordinator: 1' flag to OperationSessionInfoFromClient and parse it in the service entry point Created: 22/Jun/18 Updated: 29/Oct/23 Resolved: 14/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:DistributedCommit | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-08-27 |
| Participants: |
| Description |
|
Mongos should pass a 'coordinator: 1' flag to a participant shard of a transaction to indicate that mongos has chosen that shard to be the distributed commit coordinator for the transaction. The presence of this flag on a request should cause the shard to install a TransactionCoordinator on its Session. |
| Comments |
| Comment by Githook User [ 14/Aug/18 ] |
|
Author: {'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi'}Message: |