[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 |
| 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 |