[SERVER-28494] Fix globalLock.activeClients.total server status section Created: 24/Mar/17  Updated: 30/Jul/18  Resolved: 23/Jul/18

Status: Closed
Project: Core Server
Component/s: Concurrency, Storage
Affects Version/s: None
Fix Version/s: 4.1.2

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Dewal Gupta
Resolution: Done Votes: 1
Labels: neweng, nyc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by DOCS-10003 Clarification needed for serverStatus... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2018-07-16, Storage NYC 2018-07-30
Participants:

 Description   

Currently, this stat reflects the number of "LockedClients" that the LockedClientsCursor finds (it even counts Clients in lock state kInactive). This means it includes all the internal Clients that are used by system threads, and it has only a loose connection to the stats that appear right afterwards, "globalLock.activeClients.readers" and "globalLock.activeClients.writers", since the total also includes queued reader and writers as well as inactive Clients.



 Comments   
Comment by Githook User [ 23/Jul/18 ]

Author:

{'name': 'Dewal Gupta', 'email': 'dewal.gupta@10gen.com', 'username': 'dewalg'}

Message: SERVER-28494 updated globalLock.activeClients.total to reflect number of active readers and writers
Branch: master
https://github.com/mongodb/mongo/commit/0f1e346b3bd125322903c682e570da1f7770c4da

Generated at Thu Feb 08 04:18:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.