[DOCS-3946] Document recovery procedure when one shard is dead and not repairable Created: 25/Aug/14 Updated: 11/Jan/17 Resolved: 07/Feb/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | v1.3.7 |
| Fix Version/s: | 01112017-cleanup |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kevin J. Rice | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 1 week, 5 days ago | ||||
| Description |
|
When one shard is dead and not repairable, but you want to retain the rest of the shards, how do you do this? Tuns out there is no documentation for how to recover in this situation. I've crated the below procedure, but MongoDB should have this in the core documentation and properly vetted with correct comands, etc., and fallbacks in case a command doesn't work for some reason (i.e., stale lock). http://stackoverflow.com/questions/25490339/mongodb-recover-from-corrupted-shard/25490340#25490340 |
| Comments |
| Comment by Michael Paik [ 07/Feb/15 ] |
|
For inclusion in upcoming knowledge base. |