-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
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.
- is depended on by
-
SERVER-125827 Enable jstests that are disabled with PDIB due to lack of resumability support
-
- Closed
-
- related to
-
SERVER-128922 index_stepdown_unique.js is incompatible with primary-driven index builds
-
- Closed
-
-
SERVER-127702 Replace shared_ptr<IndexBuildInterceptor> in IndexBuildBlock with unique_ptr via idiomatic lifetime solution
-
- Backlog
-