[DOCS-2344] serverStatus "globalLock" docs are misleading Created: 04/Dec/13  Updated: 11/Jan/17  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Task Priority: Major - P3
Reporter: James Wahlin Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 10 years, 11 weeks ago

 Description   

Regarding http://docs.mongodb.org/manual/reference/command/serverStatus/#server-status-global-lock

  1. We could do a better job making clear that despite having "globalLock" in the section name, most of the metrics contained are not limited to our global lock. For example, the globalLock.currentQueue metrics provide total clients waiting on any lock, database or global. As MongoDB has received criticism in the past for having a global lock (which is no longer the case in 2.2+) we should look to clarify where possible.
  2. We describe the globalLock sections with "The globalLock data structure contains information regarding the database’s current lock state, ...". We should not use the word "database" to describe a mongod instance as this could be interpreted to mean statistics on a database contained within mongod.

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