[SERVER-4026] size of config database on shard reported in listdatabases via mongos Created: 05/Oct/11 Updated: 02/Apr/13 Resolved: 02/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Greg Studer | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
When running listDatabases through mongos, if a config database appears on a shard, information on that local config database is reported and not info about the actual config database on the config server. Since config dbs on shards are effectively masked by mongos by all other operations, probably makes sense to always report config server config db stats via mongos. |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 02/Apr/13 ] |
|
Dup of |