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

Make RangeDeleter correctly handle epoch changes due to shard key refinement

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.3
    • None
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 2019-10-07, Sharding 2019-12-02

    Description

      Right now, the range deleter uses the epoch of a collection to uniquely identify it, and if the epoch changes, it will throw out the range deletion tasks for that collection. However, now that refining the shard key changes the epoch of a collection, this logic is no longer correct and will lead to permanently orphaned documents.

      Attachments

        Activity

          People

            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            matthew.saltz@mongodb.com Matthew Saltz (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: