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

Do not use the collection distributed lock for chunk merges

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • v5.0, v4.4, v4.2, v4.0
    • Sharding EMEA 2021-05-17

    Description

      Currently chunk merges acquire the collection distributed lock. This means that it is not possible to run more than one merge at a time for the entire cluster or if there are any ongoing splits or balancing (again for the entire cluster).

      This ticket is to figure out how to remove the dist lock acquisition from merges without causing the much more expensive moves to start failing, because the chunk being moved got merged.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. SERVER-59929 unexpected slower update/insert operation bease of splitchunk and moveChunk

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Task - A task that needs to be done. SERVER-57032 Acquire only local distLock for Sharding DDL coordinators

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-56654 Do not use the collection distributed lock for chunk splits

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-57115 Merge chunks should wait for any ongoing moves to complete

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

          Task - A task that needs to be done. SERVER-25359 Create collection-specific ResourceMutex map to allow split/merge/move chunk on different collections to proceed in parallel

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-56786 There are three routing info refreshes and two chunk scans on the mergeChunks path

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: