[SERVER-84777] Ensure dbCheck reports a retryable warning upon primary step down Created: 11/Jan/24 Updated: 07/Feb/24 Resolved: 07/Feb/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.3.0-rc3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Moustafa Maher |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-855-milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2024-01-22, Repl 2024-02-05, Repl 2024-02-19 |
| Participants: |
| Description |
|
From conversations with Cloud, it seems dbCheck may not correctly log a warning health log message if the primary steps down. In addition, dbCheck does not log the dbCheckStop health log entry, indicating that dbCheck has completed. We should investigate why this is the case and make sure that the step down error is caught and reported as a warning. |
| Comments |
| Comment by Githook User [ 07/Feb/24 ] |
|
Author: {'name': 'Moustafa Maher', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}Message: GitOrigin-RevId: 72b172737f9545051c39b3e33a2f86dbf411e0ad |
| Comment by Githook User [ 28/Jan/24 ] |
|
Author: {'name': 'Moustafa Maher', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}Message: GitOrigin-RevId: b2989cdfbb86a66985f22aa0d8a4e6930118d080 |