[SERVER-24661] Secondary block reader a very long time when replay oplog Created: 20/Jun/16  Updated: 06/Dec/22  Resolved: 21/Dec/17

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

Type: Improvement Priority: Major - P3
Reporter: Zhang Youdong Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-20328 Allow secondary reads while applying ... Closed
Related
is related to SERVER-21862 Use record store directly to read fro... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Participants:
Case:

 Description   

During oplog replay,Secondary hold Lock::ParallelBatchWriterMode,which will queue all the reader, this will block the reader for a long time if the operation is time consuming. For example

1. createIndex in foreground which will take 20 minutes
2. createIndex in background which will take 20 minutes,followed by an operation which will take a database lock(eg: dropIndex)



 Comments   
Comment by Asya Kamsky [ 21/Dec/17 ]

Closing as duplicate of SERVER-20328

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