[DOCS-1076] Clarify that a long-running mongod --repair can be interrupted without corruptions Created: 31/Jan/13 Updated: 22/Feb/13 Resolved: 22/Feb/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Thomas Rueckstiess | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 10 years, 51 weeks, 6 days ago | ||||
| Description |
|
http://docs.mongodb.org/manual/reference/mongod/#cmdoption-mongod--repair We should mention that the --repair option repairs each database separately and killing the repair will not leave any databases in an inconsistent "half-repaired" state. |
| Comments |
| Comment by auto [ 22/Feb/13 ] |
|
Author: {u'date': u'2013-02-22T01:47:34Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |