[DOCS-11614] Improve Storage Watchdog Explanation Created: 16/Apr/18 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nic Cottrell | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.com/manual/administration/monitoring/index.html#storage-node-watchdog |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 0.25 |
| Description |
|
The "Storage Watchdog" section doesn't explain the purpose of this feature (e.g. to avoid a primary getting stuck and stalling the entire RS) or any side-affects to be aware of, and possible alternatives (like OS watchdog daemon). |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |