-
Type:
Bug
-
Resolution: Done
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:http://docs.mongodb.org/manual/administration/analyzing-mongodb-performance/#locking-performance
*Location*: http://docs.mongodb.org/manual/administration/analyzing-mongodb-performance/#administration-monitoring-page-faults
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.81 Safari/537.36
*Referrer*: http://docs.mongodb.org/manual/faq/storage/
*Screen Resolution*: 1440 x 900
*repo*: docs
*source*: administration/analyzing-mongodb-performance
http://docs.mongodb.org/manual/administration/analyzing-mongodb-performance/#locking-performance *Location*: http://docs.mongodb.org/manual/administration/analyzing-mongodb-performance/#administration-monitoring-page-faults *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.81 Safari/537.36 *Referrer*: http://docs.mongodb.org/manual/faq/storage/ *Screen Resolution*: 1440 x 900 *repo*: docs *source*: administration/analyzing-mongodb-performance
Hi,
http://docs.mongodb.org/manual/administration/analyzing-mongodb-performance/#locking-performance
"If globalLock.ratio is also high, MongoDB has likely been processing a large number of long running queries."
serverStatus.globalLock.ratio does not exist. It was removed from serverStatus long time ago. See
Remove globalLock.ratio from serverStatus
https://jira.mongodb.org/browse/SERVER-6838
HTH,
Pierre
Reporter: Pierre De Wilde
E-mail: pierredewilde@gmail.com