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

Journal commits in write lock stat no longer relevant

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.8.0-rc1
    • Fix Version/s: 2.8.0-rc2
    • Component/s: Diagnostics, Storage
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

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

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

      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.

        Attachments

          Activity

            People

            Assignee:
            kaloian.manassiev Kaloian Manassiev
            Reporter:
            john.morales John Morales
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: