Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-24664

Get rid of calls to ShardingState::getCollectionMetadata

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.11
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 16 (06/24/16), Sharding 17 (07/15/16), Sharding 18 (08/05/16)

      The per-collection metadata is owned and managed through the CollectionShardingState class, which has one instance per sharded collection.

      All retrieval of collection metadata should go through this class so it can enforce proper locking rules and we should remove calls to ShardingState::getCollectionMetadata, which does not check for locks.

            Assignee:
            leon.zaruvinsky Leon Zaruvinsky
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: