[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: DOCS-356 minor corrections in response to feedback
Branch: master
https://github.com/mongodb/docs/commit/5ac1b1b6ca6e9d626722fb427e125097341002b2

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: DOCS-356 repair revision
Branch: master
https://github.com/mongodb/docs/commit/6849344899df0f5411e95bcba91874f0c347f6ca

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:
Warning In general, if you have an intact replica set member, do not use db.repairDatabase() and restore from the other replica member.

VS

Bad (at least not without mentioning the above and STRONGLY discouraging this path):
Note This command will fail if your database is not a master or primary. If you need to repair a secondary or slave node, first restart the node as a standalone mongod by omitting the --replSet or --slave options, as necessary.

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.

Generated at Thu Feb 08 07:38:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.