Avoid using single-phase foreground index builds to support namespaces within the config database

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.1.0-rc1022
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Minor Change
    • ALL
    • CAR Team 2026-08-03, CAR Team 2026-08-17, CAR Team 2026-08-31, CAR Team 2026-09-14
    • 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 problematic for two reasons:

      • if the index build is aborted by a replication rollback, the related catalog entry needs to be patched with an non-timestamped  write op, triggering an invariant at WT level;
      • Single-phase foreground index builds are not compatible with mongod nodes whose persistence provider supports only primary driven index builds.

            Assignee:
            Allison Easton
            Reporter:
            Yuhong Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: