[SERVER-4976] mongostat opcounts always zero Created: 15/Feb/12 Updated: 15/Aug/12 Resolved: 20/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Tools |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tomas Pecholt | Assignee: | Ben Becker |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
WindowsXP 32b, Core i7, 3GB RAM, SSD |
||
| Attachments: |
|
| Operating System: | Windows |
| Participants: |
| Description |
|
mongostat in version 2.0.2 always shows zero insert count. In 1.8.5 the results are as expected. Updates, getmores and removes are possibly also broken. The attachments are mongostat outputs for 1.8.5 and 2.0.2 where identical set of operations was run (inserts) |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 20/Feb/12 ] |
|
thanks for looking further this is actually a dup of |
| Comment by Tomas Pecholt [ 20/Feb/12 ] |
|
Ok so here is the solution. Apply this patch (instance.cpp.diff). Would be nice to backport it to 2.0.2 |
| Comment by Tomas Pecholt [ 17/Feb/12 ] |
|
Here you go |
| Comment by Eliot Horowitz (Inactive) [ 17/Feb/12 ] |
|
Can you send the log file? |
| Comment by Tomas Pecholt [ 17/Feb/12 ] |
|
Yes I Am sure. Again when I run db.serverStatus() in 1.8.5 I get non-zero insert count (attached). Then when you look at stat-202.txt you clearly see the allocated memory is growing, there are some page faults, db is write-locked and also netIn shows there is ongoing communication between the server and client. Why would that be if there are no inserts, updates, anything? Only issue I could think of is I (mistakenly) configured my database to use "Test" name. I know there is also "test" database created by default and sometimes I get some warning from mongo.exe about that. But 1.8.5 works fine so it doesn't seem this is the problem. |
| Comment by Eliot Horowitz (Inactive) [ 16/Feb/12 ] |
|
Are you absolutely sure anything is hitting that server? You can slso try starting mongod with -vvv to see very verbose logging |
| Comment by Tomas Pecholt [ 16/Feb/12 ] |
|
mongostat version 2.0.2 mongostat --discover attached db.serverStatus() before and after run attached |
| Comment by Eliot Horowitz (Inactive) [ 15/Feb/12 ] |
|
What version of mongostat? Can you send db.serverStatus() before and after the run? |
| Comment by Tomas Pecholt [ 15/Feb/12 ] |
|
No replication and no sharding used. mongod and client run on same computer. |
| Comment by Scott Hernandez (Inactive) [ 15/Feb/12 ] |
|
Is this a slave/secondary being using replication? |