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

Make RangeDeleter correctly handle epoch changes due to shard key refinement

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.3
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      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

          Issue Links

            Activity

              People

              Assignee:
              matthew.saltz Matthew Saltz
              Reporter:
              matthew.saltz Matthew Saltz
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: