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

The profile command should not take a MODE_X db lock at level 0

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query

    Description

      At level 0 we are either setting the slowms or sampleRate global values which does not require a database lock or if the database exists, setting the profiling level to 0 which requires at most a MODE_S lock.

      It is worth noting that Locker and RecoveryUnit stashing for transactions will block MODE_X acquisition on a participating database. This will make this issue more visible for those using transactions.

      Attachments

        Activity

          People

            backlog-server-query Backlog - Query Team (Inactive)
            james.wahlin@mongodb.com James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: