Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-16328

Journal commits in write lock stat no longer relevant

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.8.0-rc2
    • Affects Version/s: 2.8.0-rc1
    • Component/s: Diagnostics, Storage
    • Labels:
      None
    • ALL
    • Hide

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

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

      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.

            Assignee:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Reporter:
            john.morales@mongodb.com John Morales (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: