[SERVER-18506] Balancer section of printShardingStatus should respect passed-in configDB Created: 17/May/15 Updated: 13/Oct/15 Resolved: 10/Jul/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding, Shell |
| Affects Version/s: | 3.0.0, 3.1.0 |
| Fix Version/s: | 3.0.7, 3.1.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Kevin Pulo |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Completed: | |||||||||
| Sprint: | Sharding 6 07/17/15 | ||||||||
| Participants: | |||||||||
| Description |
|
Support often needs to analyse dumps of the config database. This usually involves running sh.status()/printShardingStatus() and passing in a reference to the mongorestored configDB, e.g. printShardingStatus(db.getSiblingDB("the_config_dump")) However, the "Balancer" section (added in This means that if a database with a name other than "config" is passed in, then most of the output will relate to the correct db, but the balancer section will relate to the db named "config", which could have completely different details. Furthermore, if there is no db named "config" then printShardingStatus() will print mysterious warnings about config.settings and/or config.locks being missing, even though they are present in the given configDB. This is all very confusing and misleading when trying to analyse a config dump. |
| Comments |
| Comment by Githook User [ 23/Sep/15 ] |
|
Author: {u'username': u'devkev', u'name': u'Kevin Pulo', u'email': u'kevin.pulo@mongodb.com'}Message: (cherry picked from commit e8251c03db4c43d7127c1e8d8e306d8bfb688b0d) |
| Comment by Githook User [ 10/Jul/15 ] |
|
Author: {u'username': u'devkev', u'name': u'Kevin Pulo', u'email': u'kevin.pulo@mongodb.com'}Message: |