Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 9.0.0-rc0
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Backwards Compatibility:
Fully Compatible
Sprint:
Storage Execution 2026-03-16, Storage Execution 2026-03-30
Linked BF Score:
0
CAR Domain/s:
None

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

Secondaries should not need an index builder thread at all for primary-driven index builds, so we should be able to remove it.

depends on

SERVER-114225 Create class for initializing temporary tables created during index builds

Closed

is depended on by

SERVER-120549 LOGV2_FATAL 7329403 "Received an index build commit from the primary for an index build that we were unable to build successfully" in mongo::ReplIndexBuildState::tryCommit

Closed

is duplicated by

SERVER-120549 LOGV2_FATAL 7329403 "Received an index build commit from the primary for an index build that we were unable to build successfully" in mongo::ReplIndexBuildState::tryCommit

Closed

is related to

SERVER-122546 Exit builder thread upon step down with PDIB

Open

SERVER-121344 Run abort_primary_driven_index_build_if_interrupted_by_failover.js both with and without a secondary restart

Closed

related to

SERVER-122206 Complete TODO listed in SERVER-111304

Open

SERVER-112287 Investigate the possibility and if so, consequences of failing to abort an index on step up for primary driven index builds

Closed

(2 related to)

Assignee:: Gregory Noma
Reporter:: Sandeep Dhoot (Inactive)
Participants:: Githook User, Gregory Noma, Sandeep Dhoot
Votes:: 1 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Sep 22 2025 08:17:45 PM UTC
Updated:: Apr 07 2026 03:03:11 PM UTC
Resolved:: Mar 19 2026 02:46:46 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates