[SERVER-30422] Make dbCheck use new health log Created: 31/Jul/17 Updated: 30/Oct/23 Resolved: 22/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.13 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Kuehne | Assignee: | Ian Kuehne |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Storage 2017-08-21, Storage 2017-09-11 |
| Participants: |
| Description |
|
Now that we have a workable local health log (in review), we can update dbCheck to log conclusions into it. We'll need to correspondingly change the command's return value. |
| Comments |
| Comment by Githook User [ 22/Aug/17 ] |
|
Author: {'username': 'ikuehne', 'email': 'ian.kuehne@mongodb.com', 'name': 'Ian Kuehne'}Message: Also includes fixes for |