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

Range deleter must start with same range deletion task on step up

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Fully Compatible
    • Sharding EMEA 2022-04-04, Sharding EMEA 2022-04-18
    • 135

      Currently, there is no guarantee that range deletions will continue to process the same range after step up that was being processed before step down. This causes a problem for tracking orphaned documents because if an update to the orphan count is missed due to a step down, the document could be processed after all other range deletions, potentially leaving a stale orphan count for a very long time.
      To fix this, we should ensure that the same range deletion document that was being processed on step down is also processed on step up. This way an inaccurate orphan count will be fixed quickly.

            Assignee:
            allison.easton@mongodb.com Allison Easton
            Reporter:
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: