[SERVER-29557] Allow healthy databases to skip repairs Created: 12/Jun/17 Updated: 06/Dec/22 Resolved: 23/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Chris Kuethe | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
As a complement to Unfortunately, while attempting to repair some another database in this instance I hit some assertion failure which stopped the entire repair process, rather unnecessarily, i think. Now when I restart the repair, I'm going to waste another few hours waiting for a_big_database to repair unnecessarily before I can get around to repairing some_other_big_database which is what I really care about. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 23/Jun/17 ] |
|
Chris, we've linked a project we have scheduled to improve database repair ( |
| Comment by Mark Agarunov [ 16/Jun/17 ] |
|
Hello chris.kuethe@gmail.com, After taking another look at this, I believe you are correct that this is related and not a duplicate. I've reopened the ticket and set the fixVersion to "Needs Triage" for this new feature to be scheduled against our currently planned work. Updates will be posted on this ticket as they happen. Thanks, |
| Comment by Chris Kuethe [ 15/Jun/17 ] |
|
I'd call it related, but not duplicate. Like a file system, you could keep a clean/dirty bit on each database or collection which would be the first write when a database opens and is changed and the last write before it closes (or the last write after changes are committed). |
| Comment by Mark Agarunov [ 13/Jun/17 ] |
|
Hello chris.kuethe@gmail.com, Thank you for the report. The behavior you've detailed appears to be the same as the issue in Thanks, |