Switch AutoGetCollectionForReadMaybeLockFree for acquireCollectionsMaybeLockFree in DocumentSourceCursor

XMLWordPrintableJSON

    • Sharding NYC
    • Sharding EMEA 2023-10-02
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The current multi-collection acquire path offered by AutoGetCollectionForReadLockFree violates a fundamental sharding requirement that all referenced namespaces pre-declare a placement concern (db or shard version). Because of this, they are not safe to use with a concurrent shardCollection or movePrimary.

      This ticket is to switch the two usages in DocumentSourceCursor to the new acquisitions API.

              Assignee:
              [DO NOT USE] Backlog - Sharding NYC
              Reporter:
              Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: