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

Defragmenter should not retry StaleShardVersion

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.3.0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-02-07, Sharding EMEA 2022-02-21
    • 59

    Description

      If a chunk migration is submitted with the bounds of a chunk that no longer exists, theĀ error returned is a stale shard version error. The defragmentation algorithm is currently using stale shard version errors to trigger retrieving the new shard version, but is keeping the in memory state of the phase and issuing the same request with the new shard version.

      In the case of a chunk whose bounds have changed, though, this means the same movechunk request will be continuously issued and failed. We need to either not count stale shard versions as retriable, or somehow distinguish between actual stale shard version errors and chunk boundary errors.

      Attachments

        Activity

          People

            tommaso.tocci@mongodb.com Tommaso Tocci
            allison.easton@mongodb.com Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: