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

Use the resharding-specific refresh function when recovering a resharding operation in the drain mode

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • Sharding EMEA 2021-05-17

    Description

      When we recover the resharding ops in the drain mode we do a refresh of the collection. This refresh may hang here, because the in-memory critical section was already retaken and it will be released once the resharding operation is completed.

      The proposed solution is calling this resharding-specific function instead of the generic one.

      This issue was introduced when we replaced the in-memory critical sections by recoverable critical sections in SERVER-53653.

      Attachments

        Issue Links

          is related to

          Task - A task that needs to be done. SERVER-53653 [Resharding] Take the critical section when renaming on recipient shards

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-56638 Fix flushReshardingStateChanges critical section race

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
              sergi.mateo-bellido@mongodb.com Sergi Mateo Bellido
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: