Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-1362

Possible to call db.fsyncLock() while profiling is enabled

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v1.3.9
    • Component/s: manual
    • Labels:
      None
    • Last comment by Customer:
      true
    • Actual Time:
      4

      Description

      The db.fsyncLock() docs say:

      Note: The database cannot be locked with db.fsyncLock() while profiling is enabled. You must disable profiling before locking the database with db.fsyncLock(). Disable profiling using db.setProfilingLevel() as follows in the mongo shell...

      I was able to lock a 2.4.1 database while profiling was enabled (mode 2). Issuing queries while locked resulted in no new data entering the system.profile collection, and once the DB was unlocked, profiling continued as expected.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              michael.paik Michael Paik
              Reporter:
              jmikola Jeremy Mikola
              Participants:
              Last commenter:
              Jonathan Dahl Jonathan Dahl
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                6 years, 51 weeks, 6 days ago
                Date of 1st Reply: