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
    • None
    • 3
    • None
    • 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:
              [DO NOT USE] Backlog - Catalog and Routing
              Reporter:
              Daniel Gomez Ferro
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: