[SERVER-43083] Fail prepareTransaction if coordinator shard does not exist in shard registry Created: 29/Aug/19 Updated: 06/Dec/22 Resolved: 03/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
Once we send the coordinator shard with the prepareTransaction command, participants should check that the coordinator shard exists in the shard registry. If it does not, they should fail the command. This is to prevent against a race that could occur after removing a shard. The shard registry refresh killing transactions whose coordinator shard was removed can race with the prepareTransaction command reaching a participant. |
| Comments |
| Comment by Sheeri Cabral (Inactive) [ 03/Jan/20 ] |
|
We have abandoned the project associated with this work - PM-1477. |