[DOCS-356] repairDatabase stuff Created: 23/Jul/12 Updated: 08/Sep/12 Resolved: 24/Jul/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 30 weeks, 1 day ago |
| Description |
|
there are some inconsistencies between http://docs.mongodb.org/manual/reference/javascript/?highlight=repair#db.repairDatabase and http://docs.mongodb.org/manual/reference/commands/#repairDatabase. I'd suggest merging them and making sure to STRONGLY discourage the use of repair in favor of restoring from a recent backup or resyncing from a replica. Also http://docs.mongodb.org/manual/reference/mongod/?highlight=repair#cmdoption-mongod--repair should be merged in and have the same warnings. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 24/Jul/12 ] |
|
please reopen if you think additional changes are required. |
| Comment by auto [ 24/Jul/12 ] |
|
Author: {u'date': u'2012-07-24T06:40:37-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by auto [ 24/Jul/12 ] |
|
Author: {u'date': u'2012-07-23T19:09:15-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by Sam Kleinman (Inactive) [ 24/Jul/12 ] |
|
https://github.com/mongodb/docs/pull/84 Please review and comment. This is probably not the most ideal form for this information, and a more full revision will be useful shortly, but it's more consistent and clear on the most salient points. Will merge and publish in the morning. |
| Comment by Scott Hernandez (Inactive) [ 23/Jul/12 ] |
|
Mathias, that was for the docs team to indicate we need to include that material. |
| Comment by Mathias Stearn [ 23/Jul/12 ] |
|
Yes, yes, but they need to be everywhere and not offer conflicting advice. EG: Good: VS Bad (at least not without mentioning the above and STRONGLY discouraging this path): Or am I misunderstanding what you meant? |
| Comment by Scott Hernandez (Inactive) [ 23/Jul/12 ] |
|
The comments, warnings, and sections in the docs here are there for a reason, we need to copy them over, or link to them. |