-
Type: Bug
-
Resolution: Incomplete
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.0.6, 2.1.2
-
Component/s: Sharding
-
None
-
ALL
When a migration fails it can leave behind orphaned documents. We should clean those up in the background after we detect that the migration has failed.
Currently you can get errors if you try to insert a new document onto the shard with orphaned documents and the new document has the same key as an orphaned document on a field with a unique index (like _id).
- is duplicated by
-
SERVER-26316 cleanupOrphaned command is too slow
- Closed
-
SERVER-14117 moveChunk should attempt to retry write errors during chunk cleanup
- Closed
- related to
-
SERVER-8598 Add command to cleanup orphaned data created by failed chunk migrations
- Closed