Move sharding placement checks from opobservers to restore from yield

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2025-09-29, CAR Team 2025-10-13, CAR Team 2025-10-27, CAR Team 2025-11-10
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      We are performing sharding placement checks (dbVersion and shardVersion) on op_observers, once per affected document.

      Once all write paths use collectionAcquisitions it is no longer necessary to check on the op_observers – collectionAcquisition's restore procedure already rechecks after a yield.

            Assignee:
            Jordi Serra Torrens
            Reporter:
            Daniel Gomez Ferro
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: