v9 reports ConflictingOperationInProgress as wrong error code

ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 9.0.2
    • Component/s: None
    • Catalog and Routing
    • ALL
    • CAR Team 2026-09-28
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Server v9 reports this error on consecutive `moveChunk` commands that trigger conflicts:

      (OperationFailed) Command request failed on source shard. :: caused by :: Data transfer error: migrate failed: ConflictingOperationInProgress: Migration aborted: committing it would drop point-in-time reachable ownership history for a chunk only partially covered by source chunk [{ _id: 50 }, { _id: MaxKey }). Set the allowMigrationsToDropRecipientPITHistory server parameter to bypass this check.

      OperationFailed is code 96. v8, though, reported code 117 for the same circumstance.

      This blocks mongosync’s v9 support because it makes mongosync’s test suite crash rather than retry the error.

            Assignee:
            Wolfee Farkas
            Reporter:
            Felipe Gasper
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: