[SERVER-42369] Ensure all shards eventually refresh metadata after shard key refine Created: 23/Jul/19 Updated: 06/Dec/22 Resolved: 13/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
To ensure shards eventually pick up the new shard key after a shard key refine, during _configsvrRefineCollectionShardKey an asynchronous task resilient to failover should be launched that is guaranteed to trigger a refresh for the refined collection if the shard key refine succeeds and becomes majority committed. This should use the PersistentTaskQueue from the resumable range deleter project. |
| Comments |
| Comment by Jack Mulrow [ 13/Aug/19 ] |
|
Because of the changes fromĀ |