Index builds interrupted for rollback may be resumed incorrectly on primary driven index builds

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Storage Execution 2026-02-16
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When primary steps down, if it has to rollback, it stops all active index builds by calling stopIndexBuildsForRollback. Unlike handling kOplogAbort, in which a secondary is told to abort and clean up the index build; for kRollbackAbort we take care to preserve the state by calling abortIndexBuildWithoutCleanup. After rollback we'll restart or resume the index builds. This can potentially lead to problems since I suspect it will start a hybrid index build on a secondary.

            Assignee:
            Malik Endsley
            Reporter:
            Wei Hu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: