establishConsistentCollection does not handle concurrent multikeyness changes

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • ALL
    • CAR Team 2026-04-27
    • 200
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-96916 enforced stricter checks in establishConsistentCollection, assuming the commit pending entry always represents what the storage transaction will commit.

      However, this is currently not true for multikey index builds committing. And it is possible that CRUD multikeyness changes may also need some work.

      The issue with index build commit is that it reuses the same CRUD path which sets multikeyness in an onCommit hook. For the commit case this should not be necessary, as the collection MODE_X lock is held. 

            Assignee:
            Yujin Kang Park
            Reporter:
            Yujin Kang Park
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: