Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
- index-builds
- storex-ranked

Assigned Teams:

Storage Execution
Operating System:
ALL
Linked BF Score:
200
CAR Domain/s:
None

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

Single-phase foreground index builds are used for internal collections, like config.shard.catalog.chunks. The index build writes to the catalog after creating the new idents, with a timestamp gotten from a no-op oplog entry, but for rare cases of abort, the write to remove the index entry from the catalog is not timestamped. This write triggers the wt check to ensure no untimestamped writes after timestamped writes.

is related to

SERVER-132525 Use Primary Driven Index Build for sharding collections when the persistence provider doesn't support other index build types

In Code Review

related to

SERVER-128952 Rollback-to-stable causes untimestamped _mdb_catalog writes for unfinished single-phase indexes

Backlog

SERVER-130850 Non-timestamped writes within foreground index builds lead to server crash while attempting to repair the catalog during a rollback

Backlog

SERVER-132958 Config server fasserts on step-up after binary upgrade to 9.0.0-rc1017: aborting the new unique config.shards.uuid_1 index build commits an untimestamped _mdb_catalog write

Closed

Assignee:: Unassigned
Reporter:: Yuhong Zhang
Participants:: Yuhong Zhang
Votes:: 0 Vote for this issue
Watchers:: 7 Start watching this issue

Created:: Jul 23 2026 06:11:01 PM UTC
Updated:: Aug 07 2026 12:50:27 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates

PagerDuty