[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.
2. enable sharding, shard a collection, create some chunks.
3. connect a shell (through mongos), call printShardingStatus(); a few times

vsize on "first" config server in cfg server list has much higher vsize than others:

config1: 4.08gb
config2: 2.56gb
config3: 2.56gb

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.

Tue Mar 4 15:04:33.011 [conn169143] command config.$cmd command: { group: { $reduce: function (doc, out) {out.nchunks++;}, ns: "chunks", cond: { ns: "database.collection" }, key: { shard: 1 }, initial: { nchunks: 0 } } } ntoreturn:1 keyUpdates:0 numYields: 4 locks(micros) r:385815 reslen:2321 226ms

That groupby command is part of the printShardingStatus() command in the shell.



 Comments   
Comment by Jared Rosoff [ 04/Mar/14 ]

possibly resolved by SERVER-10596
will test that next

Generated at Thu Feb 08 03:30:26 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.