[SERVER-1750] mongostat <ops/query/update>/sec incorrect Created: 07/Sep/10  Updated: 17/Apr/13  Resolved: 07/Sep/10

Status: Closed
Project: Core Server
Component/s: Tools
Affects Version/s: 1.7.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to TOOLS-53 Mongostat X/s should be active + comp... Closed
Operating System: ALL
Participants:

 Description   

The values should be the number of items per second, not the new items per second.

If you have 5 queries/ops running for 3 seconds you should not see 5, 0, 0 for the first, second, and third lines for that metric (where each line is at 1 second intervals).

If there are N queries/ops running for a long period of time it should never report 0 for any of those intervals during that period.

See Aaron's comment from http://jira.mongodb.org/browse/SERVER-1745



 Comments   
Comment by Eliot Horowitz (Inactive) [ 01/Oct/10 ]

Sure - another ticket is fine - but the odds of changing are incredibly small.
We are going to add an active ops field though

Comment by Scott Hernandez (Inactive) [ 01/Oct/10 ]

I'd like to re-open this one and try to collect some votes. Do you want it re-submitted as an enhancement instead of as something broken?

Comment by Ethan Gunderson [ 13/Sep/10 ]

I'm going to have to agree with Scott, this behavior was not what I expected.

Comment by Scott Hernandez (Inactive) [ 07/Sep/10 ]

It is not what I expected. I expected that it would list the number of active queries/ops in that second; that would be like any other counter or metric in another server.

I don't expect to see 0s when things are active.

I'm not sure what it is your want me to ask for.

I want the number of ops that end within that interval + active ops at the end of the interval.

Comment by Eliot Horowitz (Inactive) [ 07/Sep/10 ]

I think the current behavior is what people want/expect.
We list the queue lengths, we could list total # of readers currently perhaps.
If you think that would make sense - should make a separate ticket.

Note: its not "new" but completed.

Generated at Thu Feb 08 02:57:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.