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

Better synchronization between collection shard and drop

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.6, 3.5.9
    • Component/s: Sharding
    • Labels:
    • ALL
    • Sharding 2017-07-31
    • 0

      Currently, the 'shardCollection' command's checking/refresh phase is not protected by a distributed lock.

      This means that while that phase is performing a refresh, a concurrent drop can wipe out the chunks from underneath. Moving the distributed lock acquisition to happen inside the command itself should take care of this problem.

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

              Created:
              Updated:
              Resolved: