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

Starting and finishing chunk migration takes Global S lock

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • 3.0.14, 3.2.11
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      In MongoDB 3.2 and earlier the shards take Global S lock during migration of chunks out of a shard. This happens both in the beginning and at completion.

      Given that migrations are per collection, we should be able to only use collection X or S lock instead.

      This problem does not apply to version 3.4 where the chunk migration code was changed significantly.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: