-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Concurrency, Replication
-
None
-
Storage Execution
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.
- depends on
-
SERVER-26005 FTDC shouldn't conflict with secondary application
- Closed
- related to
-
SERVER-38341 Remove Parallel Batch Writer Mutex
- Closed