[SERVER-42500] Best effort trigger shard refreshes after refining a collection's shard key Created: 30/Jul/19 Updated: 29/Oct/23 Resolved: 06/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | James Heppenstall (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2019-08-12 | ||||||||
| Participants: | |||||||||
| Description |
|
So shards quickly pick up a new shard key, after refineCollectionShardKey updates the metadata for a collection, it should trigger refreshes on each shard that contains chunks for the refined collection. This isn't necessary for correctness, so triggering the refreshes can be best-effort and refineCollectionShardKey should return without waiting for each refresh to complete.
|
| Comments |
| Comment by Githook User [ 06/Aug/19 ] |
|
Author: {'name': 'Jamie Heppenstall', 'email': 'jamie.heppenstall@mongodb.com', 'username': 'JamesHeppenstall'}Message: |