[SERVER-40806] Router should choose first *write* participant shard as transaction recovery shard Created: 24/Apr/19 Updated: 29/Oct/23 Resolved: 29/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:ReadOnly | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2019-05-06 |
| Participants: |
| Description |
|
Until now, the first participant has been both the recovery shard and coordinator shard. With the single-write-shard implementation of first sending commit to read-only shards, then sending commit to the write-shard, it is unsafe for the first participant to be used as a recovery shard. This is because the first participant may be read-only. Instead, the first write participant will be the recovery shard. |
| Comments |
| Comment by Githook User [ 01/May/19 ] |
|
Author: {'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}Message: |
| Comment by Githook User [ 29/Apr/19 ] |
|
Author: {'name': 'Esha Maharishi', 'username': 'EshaMaharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |