[SERVER-83653] Report dbCheck retryable issues Created: 28/Nov/23 Updated: 04/Jan/24 Resolved: 04/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Xuerui Fa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-855-milestone-2 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Repl 2023-12-11, Repl 2023-12-25, Repl 2024-01-08 | ||||
| Participants: | |||||
| Linked BF Score: | 114 | ||||
| Description |
|
Currently, dbCheck does not distinguish between retryable issues and inconsistency issues in the health log. Both will result in an error health log entry. We should mark errors that are retryable within the health log, so that users know how to handle the logs. |
| Comments |
| Comment by Githook User [ 04/Jan/24 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: GitOrigin-RevId: c11ffe929ac558674e91845caf26aa8cbc6e3dbf |