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

Dropping unsharded collection fails to synchronize with a concurrent shardCollection

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.5.8
    • 3.5.6
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2017-05-08
    • 0

    Description

      Currently the sharded collection drop code path branches for sharded or unsharded collections when in practice there is no reason why it should not be the same for both.

      This causes race conditions between dropping an unsharded collection and sharding the same collection concurrently, because dropping the unsharded collection will not take the distributed lock.

      Making both of them go through the catalog client also helps with moving that command to the config server primary.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: