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

Get rid of calls to ShardingState::getCollectionMetadata

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.3.11
    • Sharding
    • None
    • Fully Compatible
    • Sharding 16 (06/24/16), Sharding 17 (07/15/16), Sharding 18 (08/05/16)

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: