Loading...

XML

Word

Printable

JSON

Details

Type: Improvement
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: 3.2.7
Component/s: Concurrency, Replication
Labels:
None

Assigned Teams:

Replication
Backwards Compatibility:
Fully Compatible
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）

Attachments

Issue Links

duplicates

SERVER-20328 Allow secondary reads while applying oplog entries

Closed

is related to

SERVER-21862 Use record store directly to read from oplog for replication

Closed

Activity

People

Assignee:: Backlog - Replication Team

Reporter:: Zhang Youdong

Participants:: Asya Kamsky, Backlog - Replication Team, Zhang Youdong

Votes:: 0 Vote for this issue

Watchers:: 12 Start watching this issue

Dates

Created:: Jun 20 2016 07:11:42 AM UTC

Updated:: Dec 06 2022 04:23:35 AM UTC

Resolved:: Dec 21 2017 09:31:17 PM UTC