[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: |
|
||||||||||||||||||||
| 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. |