[SERVER-16328] Journal commits in write lock stat no longer relevant Created: 25/Nov/14 Updated: 11/Jul/16 Resolved: 03/Dec/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Storage |
| Affects Version/s: | 2.8.0-rc1 |
| Fix Version/s: | 2.8.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | John Morales | Assignee: | Kaloian Manassiev |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Steps To Reproduce: | > db.serverStatus().dur.commitsInWriteLock |
||||
| Participants: | |||||
| Description |
|
The concept and counter of "journal commits in write lock" ("serverStatus.dur.commitsInWriteLock") appears to no longer be relevant for server 2.8, as the counter now looks to be ticked for every commit. For backward compatibility, perhaps we should keep exposing the stat but stop tracking it such that it's always zero. |
| Comments |
| Comment by Githook User [ 03/Dec/14 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: No longer relevant with the introduction of the flush lock. |