[SERVER-14393] Refresh the config metadata before sharding a collection Created: 30/Jun/14  Updated: 06/Dec/22  Resolved: 14/Jun/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.4.8, 2.6.3
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Alexander Komyagin Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Sharding
Participants:

 Description   

Right now mongoS doesn't automatically refresh the config metadata prior to sharding a collection. It might cause certain operational inconvenience e.g. if you have multiple mongoS instances and you drop the collection on one of them - you won't be able to re-shard it on any other mongoS.



 Comments   
Comment by Kaloian Manassiev [ 14/Jun/18 ]

With the moving of the shardCollection operation to the config server, this is already done.

Generated at Thu Feb 08 03:34:43 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.