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

Optimize the Range Deleter speed

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.19, 3.4.13, 3.6.3
    • Fix Version/s: 3.4.17, 3.6.7, 4.0.1, 4.1.1
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Minor Change
    • Backport Requested:
      v4.0, v3.6, v3.4
    • Sprint:
      Sharding 2018-04-09, Sharding 2018-05-07, Sharding 2018-05-21, Sharding 2018-06-04, Sharding 2018-06-18
    • Case:
    • Linked BF Score:
      0

      Description

      The sharding range deleter was intentionally implemented to not be fully efficient in order to minimize its interference with MMAP V1. This causes orphaned data to accumulate especially with the recent moveChunk improvements.

      With the WiredTiger storage engine, we can let it run at full speed and we should investigate the benefit of directly instantiating an auto-yielding delete stage instead of recreating the index scan phase for each document.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kevin.pulo Kevin Pulo
              Reporter:
              kaloian.manassiev Kaloian Manassiev
              Participants:
              Votes:
              2 Vote for this issue
              Watchers:
              18 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: