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

IndexBuildsCoordinator removes interrupted index build at shutdown on secondary

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.1, 4.3.1
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      Execution Team 2019-08-26, Execution Team 2019-09-09
    • Linked BF Score:
      32

      Description

      Part of the shutdown procedure on a secondary node in a replica set involves interrupting all active index builds. These interrupted index builds will be restarted on the next server startup. In certain situations, the abort mechanism in the IndexBuildsCoordinator may erroneously cause an active index build to be cleaned up in a non-restartable state.

      ----- OLD DESCRIPTION BELOW -----
      MultiIndexBlock::insertAllDocuments() may erroneously return IndexBuildAborted instead of an InterruptedAtShutdown. This can happen if we check the index build's internal state in _getState() before checking the OperationContext.

        Attachments

          Activity

            People

            Assignee:
            benety.goh Benety Goh
            Reporter:
            benety.goh Benety Goh
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: