-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
CAR Team 2026-08-03, CAR Team 2026-08-17
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Sharding related collections (like config.shard.catalog.chunks) have been using the single-phase foreground index build, which builds the index first on the primary completely, and then on the standbys after replicating the oplog entry. This is not compatible when the persistence provider only supports primary driven index builds.
- is duplicated by
-
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
-
- related to
-
SERVER-132135 Single-phase foreground index builds write to catalog without timestamp for abort
-
- 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
-