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

Audit all background tasks and decide which should conflict with replication application

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Do
    • None
    • None
    • Concurrency, Replication
    • None

    Description

      Currently all background tasks that ever acquire the global lock in any mode conflict with secondary application due to the PBWM lock. SERVER-26005 will make the FTDC thread not conflict. We should also audit all other background jobs and decide which ones should be able to run concurrently with a replication batch. For example, the ClientCursorMonitor thread should be able to run concurrently with replication, but the readConcern=majority SnapshotThread should not.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              mathias@mongodb.com Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: