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

Optimize the Range Deleter speed

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.17, 3.6.7, 4.0.1, 4.1.1
    • Affects Version/s: 3.2.19, 3.4.13, 3.6.3
    • Component/s: Sharding
    • Labels:
    • Minor Change
    • v4.0, v3.6, v3.4
    • Sharding 2018-04-09, Sharding 2018-05-07, Sharding 2018-05-21, Sharding 2018-06-04, Sharding 2018-06-18
    • 0

      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.

            Assignee:
            kevin.pulo@mongodb.com Kevin Pulo
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            2 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: