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

NotAllowedOnShardedCollectionCmd should be versioned

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.5.13
    • 3.5.10
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2017-08-21, Sharding 2017-09-11

    Description

      Despite intending to prevent commands that extend it from running on sharded collections, NotAllowedOnShardedCollectionCmd can run concurrently (i.e. race) with shardCollection.

      To counter this, it should take the same (dist)lock as shardCollection.

      Particularly, this will prevent convertToCapped (which, notably, changes the collection's UUID because it uses cloneCollectionAsCapped (which creates a cloned collection with a different UUID) + renameCollection under the hood) and group from running on sharded collections.

      Attachments

        Activity

          People

            hugh.han Hugh Han
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: