[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:
Gantt Dependency
has to be done before SERVER-42369 Ensure all shards eventually refresh ... Closed
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.

SERVER-42369 tracks the work to guarantee these refreshes are eventually triggered.



 Comments   
Comment by Githook User [ 06/Aug/19 ]

Author:

{'name': 'Jamie Heppenstall', 'email': 'jamie.heppenstall@mongodb.com', 'username': 'JamesHeppenstall'}

Message: SERVER-42500 Trigger best-effort shard refreshes after refineCollectionShardKey
Branch: master
https://github.com/mongodb/mongo/commit/56d4a5de827097ce127f1e8f07aa86d39e7860a7

Generated at Thu Feb 08 05:00:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.