[SERVER-29553] Add a single database repair option Created: 11/Jun/17 Updated: 12/Jul/17 Resolved: 13/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Chris Kuethe | Assignee: | Mark Agarunov |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
when running mongod --repair I should be able to repair only a single database at a time. Some of my databases have hundreds of millions or billions of documents and take hours to repair and reindex, others are tiny and take a few milliseconds. This would also allow me to repair databases in parallel. |
| Comments |
| Comment by Chris Kuethe [ 13/Jun/17 ] |
|
That doesn't work when my server won't start up. All but one of my databases were idle (no connections, no writes since daemon start) at the time of my crash, so there should be no reason to repair/reindex them. |
| Comment by Mark Agarunov [ 13/Jun/17 ] |
|
Hello chris.kuethe@gmail.com, Thank you for the report. The db.repairDatabase command allows you to run a repair on a single database as you describe. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group. Thanks, |