[SERVER-47577] readConcernCounters metric in serverStatus Created: 15/Apr/20  Updated: 29/Oct/23  Resolved: 29/Apr/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: Lingzhi Deng
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Documented
is documented by DOCS-13622 Investigate changes in SERVER-47577: ... Closed
Backwards Compatibility: Minor Change
Sprint: Repl 2020-05-04
Participants:

 Description   

Add readConcernCounters and remove opReadConcernCounters.

"readConcernCounters": {
   "nonTransactionOps": {
       "none": NumberLong(<num>),
       "local": NumberLong(<num>),
       "available": NumberLong(<num>),
       "majority": NumberLong(<num>),
       "snapshot": {
           "withClusterTime": NumberLong(<num>),
           "withoutClusterTime": NumberLong(<num>),
        },
       "linearizable": NumberLong(<num>)
   },
   "transactionOps": {
       "none": NumberLong(<num>),
       "local": NumberLong(<num>),
       "majority": NumberLong(<num>),
       "snapshot": {
           "withClusterTime": NumberLong(<num>),
           "withoutClusterTime": NumberLong(<num>),
        }
   }
}

Commands that count toward this metric are find, aggregate, count, distinct, geoSearch and mapReduce.



 Comments   
Comment by Lingzhi Deng [ 30/Apr/20 ]

Yes, that is correct.

Comment by Bruce Lucas (Inactive) [ 30/Apr/20 ]

lingzhi.deng, I believe this is the case, but can you confirm that these are all cumulative counts since the start of the current process?

Comment by Githook User [ 29/Apr/20 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: SERVER-47577: readConcernCounters metric in serverStatus
Branch: master
https://github.com/mongodb/mongo/commit/f674117136f9b2699ab42a32f6f08f6c0b5a84b3

Generated at Thu Feb 08 05:14:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.