[SERVER-27736] DBConfig should not store unsharded collections Created: 18/Jan/17 Updated: 05/Apr/17 Resolved: 20/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.2 |
| Fix Version/s: | 3.4.2, 3.5.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Sprint: | Sharding 2017-01-02, Sharding 2017-02-13 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently DBConfig stores both sharded collections and sometimes collections which started as sharded, but became unsharded in the middle. In order to simplify this cache we should only be storing sharded collections in there. |
| Comments |
| Comment by Githook User [ 20/Jan/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: (cherry picked from commit a9d62c05f1bd56e8a52f12fd096eb4f2d07a8b23) |
| Comment by Githook User [ 20/Jan/17 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |