[SERVER-7406] async delete needs to better manage collection and index disappearing. Created: 18/Oct/12 Updated: 15/Feb/13 Resolved: 27/Dec/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When an async delete starts, it's possible that the collection and shard key index it expects could have disappeared. This isn't actually an invariant, and should be expected. http://buildlogs.mongodb.org/Linux%2032-bit%20debug/builds/2271/test/sharding/prefix_shard_key.js |