Fix dangling IndexBuildInterceptor pointer in IndexCatalogEntry after PDIB stepdown teardown

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Storage Execution 2026-06-08
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When a primary-driven index build steps down, tearDownAndUnregisterIndexBuild destroys the MultiIndexBlock and its owned IndexBuildInterceptor. However, the raw (non-owning) IndexBuildInterceptor pointer on IndexCatalogEntry was not cleared, leaving it dangling. Subsequent oplog application calling entry->indexBuildInterceptor()->sideWrite() would crash with SIGSEGV.

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

              Created:
              Updated:
              Resolved: