Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-24661

Secondary block reader a very long time when replay oplog

XMLWordPrintableJSON

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

      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）

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            zyd_com@126.com Zhang Youdong
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: