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

PBWM accounting should be separate from "Global" lock

    XMLWordPrintableJSON

Details

    • Storage Execution
    • ALL

    Description

      Currently, resourceIdParallelBatchWriterMode is a ResourceId of type RESOURCE_GLOBAL. This is problematic, as the lock stats collector overlaps this resource id with the main Global one and they show up together as simply one "Global" entry in currentOp and Top output.
      Normally this isn't too much of a problem, since the PBWM and the Global lock are acquired and released in lock step. However, it does make things very confusing when trying to diagnose certain types of problems, since WiredTiger read/write tickets are acquired in between the acquisition of PBWM and Global.

      We should change the ResourceId type so that the PBWM shows up (and accrues stats) separately from the main Global lock.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: