[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:
Related
Operating System: ALL
Steps To Reproduce:

> db.serverStatus().dur.commitsInWriteLock
12
(should be zero)

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: SERVER-16328 Get rid of commitsInWriteLock/earlyCommits MMAP V1 stats

No longer relevant with the introduction of the flush lock.
Branch: master
https://github.com/mongodb/mongo/commit/3742b75049abfdb29fe5e5fe37df0f0d7ecb2873

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