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

Range deleter must locally drop drained collections

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding EMEA
    • Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10, Sharding EMEA 2023-07-24, Sharding EMEA 2023-08-07, Sharding EMEA 2023-08-21, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18
    • 3

      When all the chunks for a collection have been moved off AND all ongoing reads on orphaned documents have drained, the range-deleter should safely be able to:

      • Stop incoming migrations for the collection
      • Drop the collection locally

      This would help avoid all the unnecessary overhead caused by the range deleter: delete the whole collection/indexes rather than doing it document by document.

            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            0 Vote for this issue
            5 Start watching this issue