[SERVER-6625] db.adminCommand('top') seems to record commands as queries Created: 27/Jul/12 Updated: 11/Jul/16 Resolved: 27/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 2.0.6, 2.1.2 |
| Fix Version/s: | 2.2.2, 2.3.2 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | William Zola | Assignee: | Shaun Verch |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
In a database where the collection 'test.gamma' does not exist, I run the following shell command: >> for( i in [ 1, 2, 3, 4,5,6,7,8,9,10]) { db.gamma.insert( {x:i}); db.gamma.count(); } I then run the following command to display the operations on that collection: >> db.adminCommand('top').totals['test.gamma']; { , , , , , , , , Note that the counts show 10 inserts 10 write locks, and also 20 read locks and 20 queries. I believe that it should show 0 queries and 10 commands. Checking with "db.serverStatus().opcounters" shows that there should be 0 queries and 10 commands. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 27/Nov/12 ] |
|
breaking out jstest to separate task: |
| Comment by auto [ 11/Nov/12 ] |
|
Author: {u'date': u'2012-10-18T21:20:01Z', u'email': u'shaun.verch@10gen.com', u'name': u'Shaun Verch'}Message: |
| Comment by auto [ 08/Nov/12 ] |
|
Author: {u'date': u'2012-10-18T21:20:01Z', u'email': u'shaun.verch@10gen.com', u'name': u'Shaun Verch'}Message: |