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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: Indexing
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Execution Team 2020-08-24

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: