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

Index build hung during startup recovery waiting for optime to be majority committed

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.7.0
    • Affects Version/s: None
    • Component/s: Index Maintenance
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Execution Team 2020-08-24

      When trying to turn on the resumable index build behavior by default, we found that it's possible for a node to be hung during startup recovery after an unclean shutdown while applying a commitIndexBuild oplog entry. The node is stuck waiting for the last optime before it established the interceptor to be majority committed even though other nodes in the replica set have applied entries from a later term than the optime the node is waiting on.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            samy.lanka@mongodb.com Samyukta Lanka
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: