add detect count for hung tasks
Subsystems (3)
v2 cover add detect count for hung tasks
Hi all,
This patchset adds a counter, hung_task_detect_count, to track the number of times hung tasks are detected.
IHMO, hung tasks are a critical metric. Currently, we detect them by periodically parsing dmesg. However, this method isn't as user-friendly as using a counter.
Sometimes, a short-lived issue with NIC or hard drive can quickly decrease the hung_task_warnings to zero. Without warnings, we must directly access the node to ensure that there are no more hung tasks and that the system has recovered. After all, load average alone cannot provide a clear picture.
Once this counter is in place, in a high-density deployment pattern, we plan to set hung_task_timeout_secs to a lower number to improve stability, even though this might result in false positives. And then we can set a time-based threshold: if hung tasks last beyond this duration, we will automatically migrate containers to other nodes. Based on past experience, this approach could help avoid many production disruptions.
Moreover, just like other important events such as OOM that already have counters, having a dedicated counter for hung tasks makes sense ;)
---
Changes since v1 [1]
====================
- hung_task: add detect count for hung tasks
- Update the changelog (per Andrew)
- Find other folks to CC (per Andrew)
[1] https://lore.kernel.org/linux-mm/[email protected]
Lance Yang (2):
hung_task: add detect count for hung tasks
hung_task: add docs for hung_task_detect_count
Documentation/admin-guide/sysctl/kernel.rst | 9 +++++++++ kernel/hung_task.c | 18 ++++++++++++++++++ 2 files changed, 27 insertions(+)
Signature · 1 line
2.45.2
PATCH v2 1/2 hung_task: add detect count for hung tasks
This commit adds a counter, hung_task_detect_count, to track the number of times hung tasks are detected.
IHMO, hung tasks are a critical metric. Currently, we detect them by periodically parsing dmesg. However, this method isn't as user-friendly as using a counter.
Sometimes, a short-lived issue with NIC or hard drive can quickly decrease the hung_task_warnings to zero. Without warnings, we must directly access the node to ensure that there are no more hung tasks and that the system has recovered. After all, load average alone cannot provide a clear picture.
Once this counter is in place, in a high-density deployment pattern, we plan to set hung_task_timeout_secs to a lower number to improve stability, even though this might result in false positives. And then we can set a time-based threshold: if hung tasks last beyond this duration, we will automatically migrate containers to other nodes. Based on past experience, this approach could help avoid many production disruptions.
Moreover, just like other important events such as OOM that already have counters, having a dedicated counter for hung tasks makes sense.
--- kernel/hung_task.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
kernel/hung_task.c +18 -0
@@ -30,6 +30,11 @@*/ static int __read_mostly sysctl_hung_task_check_count =PID_MAX_LIMIT ; +/* +* Total number of tasks detected as hung since boot: +*/ +static unsigned long __read_mostly sysctl_hung_task_detect_count; +/* * Limit number of tasks checked in a batch. *
@@ -115,6 +120,12 @@ static void check_hung_task(struct task_struct *t, unsigned long timeout)if (time_is_after_jiffies (t->last_switch_time + timeout *HZ ))return ; +/* +* This counter tracks the total number of tasks detected as hung +* since boot. +*/ + sysctl_hung_task_detect_count++; +trace_sched_process_hang (t);if (sysctl_hung_task_panic) {
@@ -314,6 +325,13 @@ static struct ctl_table hung_task_sysctls[] = { .proc_handler = proc_dointvec_minmax, .extra1 = SYSCTL_NEG_ONE, }, + { + .procname = "hung_task_detect_count", + .data = &sysctl_hung_task_detect_count, + .maxlen = sizeof(unsigned long), + .mode = 0444, + .proc_handler = proc_dointvec, + }, };static void __init hung_task_sysctl_init (void )
Signature · 1 line
2.45.2
Re: [PATCH v2 1/2] hung_task: add detect count for hung tasks
Hi Andrew,
Sorry, I made a stupid mistake :(
sysctl_hung_task_detect_count is defined as an unsigned long, so we need to use proc_doulongvec_minmax instead of proc_dointvec to handle it correctly. Could you please fold the following changes into this patch?
--- kernel/hung_task.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/hung_task.c +1 -1
@@ -330,7 +330,7 @@ static struct ctl_table hung_task_sysctls[] = { .data = &sysctl_hung_task_detect_count, .maxlen = sizeof(unsigned long), .mode = 0444, - .proc_handler = proc_dointvec, + .proc_handler = proc_doulongvec_minmax, }, };
Signature · 2 lines
Thanks, Lance
PATCH v2 2/2 hung_task: add docs for hung_task_detect_count
In reply to Lance YangThis commit introduces documentation for hung_task_detect_count in kernel.rst.
--- Documentation/admin-guide/sysctl/kernel.rst | 9 +++++++++ 1 file changed, 9 insertions(+)
Documentation/admin-guide/sysctl/kernel.rst +9 -0
@@ -401,6 +401,15 @@ The upper bound on the number of tasks that are checked. This file shows up if ``CONFIG_DETECT_HUNG_TASK`` is enabled. +hung_task_detect_count +====================== + +Indicates the total number of tasks that have been detected as hung since +the system boot. + +This file shows up if ``CONFIG_DETECT_HUNG_TASK`` is enabled. + + hung_task_timeout_secs ======================
Signature · 1 line
2.45.2