[DOCS-1024] Doc's on Global locking are wrong/unclear for db.serverStatus and mongostat Created: 22/Jan/13  Updated: 12/Feb/13  Resolved: 12/Feb/13

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

Type: Improvement Priority: Critical - P2
Reporter: David Hows Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 11 years, 1 week, 1 day ago

 Description   

The documentation for locks are unclear and in places wrong.
http://docs.mongodb.org/manual/reference/server-status/#server-status-locks

This page says that

"A field named . holds the first document in locks that contains information about the global lock as well as aggregated data regarding lock use in all databases."

My understanding from discussion in dev is that the "." database will be for the actual global level lock, rather than an aggregate.

Regarding mongostat - http://docs.mongodb.org/manual/reference/mongostat/
The doc's say "This value represents the amount of time the database had a database specific lock" - can we add some clarification to show that its only the database listed and not all databases.

Examples of these values would help immensely.



 Comments   
Comment by auto [ 12/Feb/13 ]

Author:

{u'date': u'2013-02-12T20:24:37Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-1024: clarifying language about locks in 2.2 in stats
Branch: master
https://github.com/mongodb/docs/commit/659e31913d0b430fd978688b19a9c1cd281225bd

Comment by Sam Kleinman (Inactive) [ 02/Feb/13 ]

epc this correction needs to be made before the 2.2 fork and is pretty straightforward...

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