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

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

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • 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

        Activity

          People

            randolph@mongodb.com Randolph Tan
            greg_10gen Greg Studer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: