Handle applying the setMultikeyMetadata oplog entry during logical initial sync

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2026-01-19
    • 200
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      The initial sync's oplog replay phase must tolerate the oplog entry becoming irrelevant. Since the start of initial sync cloning, the collection we've staged the setMultikeyMetadata entry for may have been replaced (renamed into), dropped, or the index may have been dropped.

            Assignee:
            Josef Ahmad
            Reporter:
            Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: