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

Make rebalance chunk requests re-entrant

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding

    Description

      Currently the 'rebalanceChunk' form of moveChunk uses the kNotIdempotent retry policy, while the 'moveChunk' form uses the kIdempotent policy. This makes the 'rebalanceChunk' form less resilient to things like config server primary failovers and network errors.

      The only difference between these two is that one has a target shard specified and the other does not. We should allow 'rebalance chunk' requests, that don't have a target shard attached, to be re-run in the case of network errors, and if there's already a 'rebalance chunk' operation in progress for that same chunk, just attach to it and return its return value when finished.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: