[SERVER-55181] NamespaceString::isNamespaceAlwaysUnsharded is not up-to-date with new system config collections Created: 14/Mar/21 Updated: 29/Oct/23 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2021-03-22 | ||||||||
| Participants: | |||||||||
| Description |
|
The NamespaceString::isNamespaceAlwaysUnsharded utility is used internally by the Sharding catalog system in order to skip shard version checks for paths which are 100% known to be internal and where the callers are not prepared to handle a StaleConfig exception. This however requires that it is kept up-to-date with new systems collections which get added and currently it lacks some of the new ones that were added, such as kShardingDDLCoordinatorsNamespace and kReshardingApplierProgressNamespace. As part of this ticket we should invert the condition so that it doesn't require every new system namespace to be explicitly added, but rather to include all of them, except for config.system.sessions. |
| Comments |
| Comment by Githook User [ 15/Mar/21 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |