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

Acquire critical section in rename "check preconditions" phase only if target not sharded

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.0.1, 5.0.11, 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • v6.0, v5.0
    • Sharding EMEA 2022-07-11, Sharding EMEA 2022-07-25

    Description

      The distributed lock is preventing overlaps between the critical section acquired by migrations and rename coordinators. As there is a plan to get rid of the distributed lock, purpose of this ticket is to acquire the critical section for the target collection only in case it is not sharded.

      This is fine because SERVER-67325 introduced the acquisition of the critical section to avoid concurrent collections creation, but if a collection is already sharded that cannot happen.

      Attachments

        Issue Links

          Activity

            People

              pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
              pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: