[SERVER-2992] mongos mongostat reporting inflated inserts Created: 24/Apr/11  Updated: 29/Feb/12  Resolved: 24/Jan/12

Status: Closed
Project: Core Server
Component/s: Sharding, Tools
Affects Version/s: 1.8.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Unassigned
Resolution: Cannot Reproduce Votes: 0
Labels: mongos, mongostat
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

Mongos/mongostat are reporting 3xinserts than what the shard is seeing. In this setup the inserts are going to a db on just one of the shards, and the updates are being split (unevenly by the app) to two of the shards. This is with no sharded collections, they are just sharded dbs and each db is on a different shard.

http://gist.github.com/bd3329ab8502ec4cbdbb



 Comments   
Comment by Scott Hernandez (Inactive) [ 03/May/11 ]

It actually seems to be just displaying the same numbers as updates when there are no inserts (but there is an upsert flag):

nsert query update delete getmore command vsize res faults netIn netOut conn repl time
27596 1 27596 0 0 4 2.66g 16m 0 4m 3k 219 RTR 13:28:47
27860 0 27860 0 0 3 2.66g 16m 0 4m 2k 219 RTR 13:28:48
28095 0 28095 0 0 3 2.66g 16m 0 4m 2k 219 RTR 13:28:49
28018 1 28018 0 0 3 2.66g 16m 0 4m 4k 219 RTR 13:28:50
28190 0 28190 0 0 3 2.66g 16m 0 4m 2k 219 RTR 13:28:51
27742 0 27742 0 0 3 2.66g 16m 0 4m 2k 219 RTR 13:28:52

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