[SERVER-13035] printShardingStatus causes high vsize on config server Created: 04/Mar/14 Updated: 07/Nov/14 Resolved: 31/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.4.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jared Rosoff | Assignee: | Jared Rosoff |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | 1. start a sharded cluster with 3 config servers. vsize on "first" config server in cfg server list has much higher vsize than others: config1: 4.08gb |
| Participants: |
| Description |
|
Noticing much higher vsize on one config server than others in cluster. In addition to higher vsize, notice some slow queries in logs which identify a groupby command.
That groupby command is part of the printShardingStatus() command in the shell. |
| Comments |
| Comment by Jared Rosoff [ 04/Mar/14 ] |
|
possibly resolved by |