[SERVER-38651] Config collections other than `config.system.sessions` are allowed to become sharded Created: 14/Dec/18 Updated: 29/Oct/23 Resolved: 14/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.9, 4.0.4, 4.1.6 |
| Fix Version/s: | 4.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | newgrad, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2019-01-14 | ||||
| Participants: | |||||
| Linked BF Score: | 52 | ||||
| Description |
|
For testing purposes, currently the config server allows any collection under the config database to become sharded when the testCommands flag has been enabled. The collection filtering metadata logic however expects config collections to never be sharded and because of this invariants. We should prohibit any config collections other than the known system ones to ever become sharded, regardless of whether the testCommands flag is enabled. |
| Comments |
| Comment by Janna Golden [ 15/Jan/19 ] |
|
This was committed under the wrong ticket. Author: {'username': 'jannaerin', 'email': 'golden.janna@gmail.com', 'name': 'jannaerin'}Message: |
| Comment by Janna Golden [ 14/Jan/19 ] |
|
Code review url: http://mongodbcr.appspot.com/216570001 |