[SERVER-6210] Clean up data left behind on shards by failed migrations and failed migration cleanups Created: 26/Jun/12  Updated: 21/Mar/18  Resolved: 21/Mar/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.0.6, 2.1.2
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Randolph Tan
Resolution: Incomplete Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-26316 cleanupOrphaned command is too slow Closed
is duplicated by SERVER-14117 moveChunk should attempt to retry wri... Closed
Related
related to SERVER-8598 Add command to cleanup orphaned data ... Closed
Operating System: ALL
Participants:

 Description   

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).



 Comments   
Comment by Gregory McKeon (Inactive) [ 21/Mar/18 ]

We're going to define a more full scope for making migrations not leave orphans in the future.

Generated at Thu Feb 08 03:11:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.