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

Chunk migration can still be running even after the moveChunk command fails with maxTimeMS timeout

    • Catalog and Routing
    • 3

      This means that running a new migration immediately after a previous one failed with timeout can fail because there's a conflicting chunk migration in progress.

            Assignee:
            Unassigned Unassigned
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: