[SERVER-31644] Rename the per-shard filtering information cache collections to be prefixed with `config.cache` Created: 19/Oct/17 Updated: 30/Oct/23 Resolved: 20/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Minor Change | ||||
| Sprint: | Sharding 2017-10-23, Sharding 2017-11-13 | ||||
| Participants: | |||||
| Description |
|
Currently the per-shard filtering information collections are all directly under the config database and are called config.collections and config.chunks. Since these collections are internal and somewhat transient (as in backup/restore ignores them), this naming causes confusion with similarly-named collection on the config server, which are critical because they contain the cluster routing metadata. Because of this, we should rename them to a prefix which removes confusion with the config server's collections. Proposed names are:
|
| Comments |
| Comment by Kaloian Manassiev [ 20/Oct/17 ] |
|
The backwards compatibility impact is set to "Minor Change", because this commit makes the secondaries chunk-aware feature in RC1 not being able to run with an RC0 primary and vice versa. |
| Comment by Githook User [ 20/Oct/17 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: |
| Comment by Steve Briskin (Inactive) [ 19/Oct/17 ] |
|
kaloian.manassiev, The backup/restore services does not currently ignore these collections. Should it? Is there any downside in not ignoring them? |