[SERVER-55072] Rename coordinator must treat the primary shard as a participant Created: 09/Mar/21 Updated: 29/Oct/23 Resolved: 09/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
The rename coordinator must not make distinctions between the primary shard and any other shard. As a precondition for a unique rename recovery procedure, include also the primary shard when sending commands to all participants to manage critical section, range deletions and local rename. |
| Comments |
| Comment by Githook User [ 09/Mar/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |