[DOCS-2871] Do not recommend --repair for corruption on replicas Created: 08/Sep/11 Updated: 04/Mar/15 Resolved: 19/Mar/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 9 years, 48 weeks ago |
| Description |
|
We probably shouldn't allow the node to rejoin the set as it is likely to be inconsistent with other members. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 19/Mar/14 ] |
|
I can't find any recommendations along these lines; if you spotted something that I missed, I'm more than happy to reopen and re-investigate. |
| Comment by Sam Kleinman (Inactive) [ 19/Mar/14 ] |
|
We're working on a revision of all of the "data recovery" tutorials, but all of the existing material is quite clear on this point. |
| Comment by Eric Milkie [ 07/Mar/14 ] |
|
If a secondary is corrupted, recommend a clean initial sync rather than running repair, which can leave the set's data inconsistent. |