[SERVER-14120] Rename Collection can be allowed in Mongos Created: 31/May/14  Updated: 19/Feb/15  Resolved: 19/Feb/15

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

Type: Improvement Priority: Major - P3
Reporter: David Murphy Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-6063 Support rename collection for sharded... Closed
Participants:

 Description   

Generally people are told we cannot rename a sharded collection. This is not strictly true, we could take a config lock and update config.collections, config.chunks to have the correct data. This should trigger a config version change that the mongos and ChunkManager would both see.



 Comments   
Comment by Scott Hernandez (Inactive) [ 19/Feb/15 ]

Dup of SERVER-6063

Comment by David Murphy [ 31/May/14 ]

No but if you this on top or renaming in each Mongod you would we already have a rename collection at the single shard level. This is extra wrapping needed to allow it at a highest level. The chunk map and the chunkManager are the biggest blockers here as it was cause bad routing plans and not return expected data due to caching

Comment by Asya Kamsky [ 31/May/14 ]

Updating the metadata for the collection would not ensure that the collection on the shards was renamed.

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