[SERVER-29257] Move shard chunk metadata persisted collections (config.chunks, config.collections) from 'config.' to 'system.' namespace Created: 17/May/17  Updated: 09/Aug/17  Resolved: 09/Aug/17

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Kaloian Manassiev
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding 2017-08-21
Participants:

 Description   

whenever the system namespace convention is decided upon.

Note: don't forget to update the dropCollection namespace check! Might be able to improve the namespace string check, i.e. add a new check for metadata



 Comments   
Comment by Kaloian Manassiev [ 09/Aug/17 ]

The config database on a sharded system always routes to the config server. Because of this, config databases on the shards are effectively not reachable in a sharded system. Therefore, there is no pressing reason for putting the sharded collections under the config.system. prefix. Given that in 3.8 we also want these collections' names to incorporate the UUID, we can postpone the rename till then and decide whether to put them under system or not at that time.

For the above reasons I am closing this ticket as 'Won't Fix' and the collections will remain as config.chunks.<namespace> and config.collections.

Generated at Thu Feb 08 04:20:20 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.