[DOCS-8815] Slight context move for "asterisks mean replication opcounts" in mongostat reference Created: 13/Sep/16  Updated: 18/Jan/18  Resolved: 18/Jan/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Akira Kurogane Assignee: Ravind Kumar (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 6 years, 4 weeks ago
Story Points: 0.5

 Description   

This concerns /manual/reference/program/mongostat/.

When mongostat is monitoring a secondary the opcounts (inserts/deletes/etc) per-sec values are displayed with an asterisk prepended to them, to indicate those are replication opcounts, rather than primary ones.

An example of the output can be seen quickly at TOOLS-1437 (It is a trivial bug reporting incorrect asterisks on 0's; ignore those.)

The asterisk meaning is explained in the current reference but confusingly put that under the sub-section for the insert counts (see red sentence) only. Please move it up to the higher scope (presumably at the blue spot) so pl

Fields

mongostat returns values that reflect the operations over a 1 second period. When mongostat <sleeptime> has a value greater than 1, mongostat averages the statistics to reflect average operations per second.

mongostat outputs the following fields: <move here?>

inserts

The number of objects inserted into the database per second. If followed by an asterisk (e.g. *), the datum refers to a replicated operation.

query

The number of query operations per second.

update

The number of update operations per second.

delete

The number of delete operations per second.

Also, rather than saying the asterisk follows the figure, it should say it is prepended / attached.



 Comments   
Comment by Akira Kurogane [ 18/Jan/18 ]

I'll close 'won't fix'. It's a trivial issue, and mongostat isn't used much.

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