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

IndexBuildsCoordinator removes interrupted index build at shutdown on secondary

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.1, 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Execution Team 2019-08-26, Execution Team 2019-09-09
    • 32

      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.

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

              Created:
              Updated:
              Resolved: