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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Concurrency, Replication
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: