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

Avoid scheduling more range deletion tasks for same range during rename

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 5.1.0, 5.0.0-rc1
    • 5.0.0-rc2, 5.1.0-rc0
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Sharding EMEA 2021-06-14

    Description

      Currently, the "idempotency" of restoreRangeDeletionTasksForRename is achieved by deleting previously "renamed" range deletion tasks and reschedule them with new migration ids. By doing so, the persistent state is clean but duplicate tasks are not unscheduled from the migration util executor.

      A better strategy would be to assign migrations id to snapshotted range deletions at an early stage and afterwards simply check if the task has been already scheduled for the target collection.

      Attachments

        Activity

          People

            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: