-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 9.0.2
-
Component/s: None
-
Catalog and Routing
-
ALL
-
🟦 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.
- related to
-
SERVER-129673 Chunk migration must fail if it risks losing recipient PIT history
-
- Closed
-
-
-
- Closed
-