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

The cluster chunks resize routine should be resilient to collection UUID changes caused by renameCollection()

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.0.0-rc6, 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • v6.0
    • Sharding EMEA 2022-05-16, Sharding EMEA 2022-05-30
    • 130

    Description

      It has been observed that the execution of renameCollection with dropTarget=true may cause ClusterChunksResizePolicy to hang the config server if the target collection is an existing sharded namespace that is currently being processed by the policy.

      The root cause of the problem is ClusterChunksResizePolicy referencing the target collection with a UUID that does not match the content of config.collections once renameCollection completes.

      Attachments

        Activity

          People

            paolo.polato@mongodb.com Paolo Polato
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: