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

XMLWordPrintableJSON

    • Catalog and Routing
    • 3
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
              Reporter:
              Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: