hung_task: add detect count for hung tasks
Subsystems (3)
cover hung_task: 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. This counter provides a straightforward way to monitor hung task events without manually checking dmesg logs.
With this counter in place, system issues can be spotted quickly, allowing admins to step in promptly before system load spikes occur, even if the hung_task_warnings value has been decreased to 0 well before.
Recently, we encountered a situation where warnings about hung tasks were buried in dmesg logs during load spikes. Introducing this counter could have helped us detect such issues earlier and improve our analysis efficiency.
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 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. This counter provides a straightforward way to monitor hung task events without manually checking dmesg logs.
With this counter in place, system issues can be spotted quickly, allowing admins to step in promptly before system load spikes occur, even if the hung_task_warnings value has been decreased to 0 well before.
--- 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
PATCH 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
Andrew Morton
maintainerQuoted 6 lines · On Tue, 22 Oct 2024 19:47:34 +0800 Lance Yang <[email protected]> wrote:
Hi all,
This patchset adds a counter,
hung_task_detect_count, to track the number of times hung tasks are detected. This counter provides a straightforward way to monitor hung task events without manually checking dmesg logs.
Quoted 8 lines
With this counter in place, system issues can be spotted quickly, allowing admins to step in promptly before system load spikes occur, even if the
hung_task_warningsvalue has been decreased to 0 well before.Recently, we encountered a situation where warnings about hung tasks were buried in dmesg logs during load spikes. Introducing this counter could have helped us detect such issues earlier and improve our analysis efficiency.
Isn't the answer to this problem "write a better parser"? I mean, we're providing userspace with information which is already available.
Hi Andrew,
Thanks a lot for paying attention!
Quoted 13 lines · Andrew Morton
Quoted 10 lines · On Tue, 22 Oct 2024 19:47:34 +0800 Lance Yang <[email protected]> wrote:
Hi all,
This patchset adds a counter,
hung_task_detect_count, to track the number of times hung tasks are detected. This counter provides a straightforward way to monitor hung task events without manually checking dmesg logs.With this counter in place, system issues can be spotted quickly, allowing admins to step in promptly before system load spikes occur, even if the
hung_task_warningsvalue has been decreased to 0 well before.
Quoted 6 lines
Quoted 4 lines
Recently, we encountered a situation where warnings about hung tasks were buried in dmesg logs during load spikes. Introducing this counter could have helped us detect such issues earlier and improve our analysis efficiency.
Isn't the answer to this problem "write a better parser"? I mean,
Yeah, I certainly agree that having a good parser is important, and I'm working on that as well ;)
Quoted 1 line
we're providing userspace with information which is already available.
IHMO, there are two reasons why this counter remains valuable:
1) It allows us to easily detect hung tasks in time before load spikes occur, using simple and common monitoring tools like Prometheus.
2) It ensures that we remain aware of hung tasks even when the hung_task_warnings value has already been decreased to 0 well before.
Thanks again for your time!
Lance
Quoted 1 line
Andrew Morton
maintainerQuoted 29 lines · On Thu, 24 Oct 2024 11:28:01 +0800 Lance Yang <[email protected]> wrote:
Hi Andrew,
Thanks a lot for paying attention!
Quoted 13 lines · Andrew Morton
Quoted 10 lines · On Tue, 22 Oct 2024 19:47:34 +0800 Lance Yang <[email protected]> wrote:
Hi all,
This patchset adds a counter,
hung_task_detect_count, to track the number of times hung tasks are detected. This counter provides a straightforward way to monitor hung task events without manually checking dmesg logs.With this counter in place, system issues can be spotted quickly, allowing admins to step in promptly before system load spikes occur, even if the
hung_task_warningsvalue has been decreased to 0 well before.Quoted 6 lines
Quoted 4 lines
Recently, we encountered a situation where warnings about hung tasks were buried in dmesg logs during load spikes. Introducing this counter could have helped us detect such issues earlier and improve our analysis efficiency.
Isn't the answer to this problem "write a better parser"? I mean,
Yeah, I certainly agree that having a good parser is important, and I'm working on that as well ;)
Quoted 6 lines
Quoted 1 line
we're providing userspace with information which is already available.
IHMO, there are two reasons why this counter remains valuable:
1) It allows us to easily detect hung tasks in time before load spikes occur, using simple and common monitoring tools like Prometheus.
But the new sysctl_hung_task_detect_count counter gets incremented a microsecond before the printk comes out. I don't understand the difference.
Quoted 2 lines
2) It ensures that we remain aware of hung tasks even when the
hung_task_warningsvalue has already been decreased to 0 well before.
That makes sense, I guess. But fleshing this out with a real operational scenario would help persuade reviewers of the benefit of this change.
So please describe the utility with full details - sell it to us!
Quoted 43 lines · Andrew Morton
Quoted 29 lines · On Thu, 24 Oct 2024 11:28:01 +0800 Lance Yang <[email protected]> wrote:
Hi Andrew,
Thanks a lot for paying attention!
Quoted 13 lines · Andrew Morton
Quoted 10 lines · On Tue, 22 Oct 2024 19:47:34 +0800 Lance Yang <[email protected]> wrote:
Hi all,
This patchset adds a counter,
hung_task_detect_count, to track the number of times hung tasks are detected. This counter provides a straightforward way to monitor hung task events without manually checking dmesg logs.With this counter in place, system issues can be spotted quickly, allowing admins to step in promptly before system load spikes occur, even if the
hung_task_warningsvalue has been decreased to 0 well before.Quoted 6 lines
Quoted 4 lines
Recently, we encountered a situation where warnings about hung tasks were buried in dmesg logs during load spikes. Introducing this counter could have helped us detect such issues earlier and improve our analysis efficiency.
Isn't the answer to this problem "write a better parser"? I mean,
Yeah, I certainly agree that having a good parser is important, and I'm working on that as well ;)
Quoted 6 lines
Quoted 1 line
we're providing userspace with information which is already available.
IHMO, there are two reasons why this counter remains valuable:
1) It allows us to easily detect hung tasks in time before load spikes occur, using simple and common monitoring tools like Prometheus.
But the new
sysctl_hung_task_detect_countcounter gets incremented a microsecond before the printk comes out. I don't understand the difference.
Quoted 8 lines
Quoted 2 lines
2) It ensures that we remain aware of hung tasks even when the
hung_task_warningsvalue has already been decreased to 0 well before.That makes sense, I guess. But fleshing this out with a real operational scenario would help persuade reviewers of the benefit of this change.
So please describe the utility with full details - sell it to us!
Thanks, the suggestion is very helpful!
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 the 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 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 ;)
Thanks,
Lance