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

Secondary block reader a very long time when replay oplog

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 3.2.7
    • None
    • Concurrency, Replication
    • None
    • Fully Compatible

    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

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              zyd_com@126.com Zhang Youdong
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: