[SERVER-26006] Audit all background tasks and decide which should conflict with replication application Created: 07/Sep/16  Updated: 06/Dec/22  Resolved: 10/Jun/19

Status: Closed
Project: Core Server
Component/s: Concurrency, Replication
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-26005 FTDC shouldn't conflict with secondar... Closed
Related
related to SERVER-38341 Remove Parallel Batch Writer Mutex Closed
Assigned Teams:
Storage Execution
Participants:

 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.



 Comments   
Comment by Eric Milkie [ 10/Jun/19 ]

We believe that effort is better spent trying to remove the PBWM.

Generated at Thu Feb 08 04:10:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.