[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: |
|
||||
| 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 |