Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Operating System:
ALL
Sprint:
Storage Execution 2026-06-08
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

A primary-driven index build interrupted by stepdown may self-abort and destroy its catalog entry instead of being preserved for resume on step-up. This occurs when something delays the build's cleanup context past re-election, causing it to incorrectly proceed with full abort. The result is that the index is never created.

duplicates

SERVER-127769 Fix primary-driven index build self-abort on stepdown to preserve catalog entry for resume

Closed

is related to

SERVER-127417 Preserve and resume primary-driven index builds across stepdown/step-up

Closed

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

Created:: May 27 2026 08:06:36 AM UTC
Updated:: Jun 02 2026 08:10:44 PM UTC
Resolved:: Jun 02 2026 08:10:40 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates