-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Description
Description:
The serverStatus sections described in the Description were added.
Engineering Ticket Description:
We will create new serverStatus sections:
opReadConcernCounters: { available: <num>, linearizable: <num>, local: <num>, majority: <num>, snapshot: <num>, none: <num> }The sum of these counters should be opCounters.query (note that this means we will not include getMore commands, since these inherit the readConcern from the originating command).
opWriteConcernCounters: { insert: { wmajority: <num>, wnum: { "0": <num>, // only generate these fields if they are used "2": <num>, ... }, wtag: { "tag1": <num>, // only generate these fields if they are used "tag2": <num>, ... } none: <num> }, update: { wmajority: <num>, wnum: { "0": <num>, // only generate these fields if they are used "2": <num>, ... }, wtag: { "tag1": <num>, // only generate these fields if they are used "tag2": <num>, ... } none: <num> }, delete: { wmajority: <num>, wnum: { "0": <num>, // only generate these fields if they are used "2": <num>, ... }, wtag: { "tag1": <num>, // only generate these fields if they are used "tag2": <num>, ... } none: <num> } }The sum of the counters for opWriteConcernCounters.insert should be opcounters.insert, and similarly for the other operations. Note that the j value is ignored, so {{
Unknown macro: {w}}} and {{
Unknown macro: {w}}} are both counted in w1.
Scope of changes
since 4.0.6,
just:
- source/reference/command/serverStatus.txt
- source/includes/extracts-server-status-projection-base.yaml
Impact to Other Docs
none - since new fields
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
- documents
-
SERVER-38998 Create serverStatus metrics for readConcern and writeConcern
- Closed
- related to
-
DOCS-12403 Docs for SERVER-39267: Guard opWriteConcernCounters behind flag
- Closed