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

Serialize scheduling of new range deletions behind range deletion to be resumed

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 6.0.0-rc0
    • Component/s: None
    • None
    • Sharding EMEA
    • ALL

      SERVER-64979 guarantees that on step-up existing range deletions will be scheduled after resuming a potential deletion that started before stepping down.

      However, since the scheduling is done asynchronously, it may happen (even if really improbable) that a migration succeeds and schedules a range deletion before the one being resumed.

      Purpose of this ticket is to ensure that also the scheduling of new range deletions serializes behind the on getting resumed.

            Assignee:
            backlog-server-sharding-emea [DO NOT USE] Backlog - Sharding EMEA
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: