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

need to check draining and potentially other shard status before auto-migrates

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Operating System:
      ALL

      Description

      While we reload shard information before running the balancer, we don't do the same for auto-migrates, and the logic for the target shard is different from the balancer policy.

      There's also a secondary race condition in that it's possible for shard status to change after shard info reload and before the migration is triggered, but this is a much rarer event and will generally be caught while waiting for draining.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              renctan Randolph Tan
              Reporter:
              greg_10gen Greg Studer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: