[SERVER-7614] Top command shouldn't require db lock Created: 10/Nov/12  Updated: 11/Jul/16  Resolved: 11/Nov/12

Status: Closed
Project: Core Server
Component/s: Admin, Concurrency
Affects Version/s: None
Fix Version/s: 2.2.3, 2.3.1

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

Makes it less useful during high lock% events.



 Comments   
Comment by auto [ 08/Jan/13 ]

Author:

{u'date': u'2012-11-11T06:47:33Z', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: top command doesn't need a global lock as it has its own SERVER-7614
Branch: v2.2
https://github.com/mongodb/mongo/commit/2d43e87a51d62e92767b08b9703596dafcfa5f52

Comment by auto [ 11/Nov/12 ]

Author:

{u'date': u'2012-11-11T06:47:33Z', u'email': u'eliot@10gen.com', u'name': u'Eliot Horowitz'}

Message: top command doesn't need a global lock as it has its own SERVER-7614
Branch: master
https://github.com/mongodb/mongo/commit/6d089c27a506d0bbb5a761b9099a16d027ffd93c

Generated at Thu Feb 08 03:15:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.