[FLINK-35160] Support for Thread Dump provides a convenient way to display issues of thread deadlocks in tasks

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.16.0, 1.17.1, 1.19.0, 1.18.1
• Component/s: Runtime / REST
• Assignee: Unassigned
• Reporter: elon_X
• Created: 18/Apr/24 13:35
• Updated: 20/Apr/24 06:43

Description

After receiving feedback from the business side about performance issues in their tasks, we attempted to troubleshoot and discovered that their tasks had issues with thread deadlocks. However, the Thread Dump entry on the Flink page only shows thread stacks. Since the users are not very familiar with Java stacks, they couldn't clearly identify that the deadlocks were due to issues in the business logic code and mistakenly thought they were problems with the Flink framework

the JVM's jstack command can clearly display thread deadlocks, unfortunately, the business team does not have the permissions to log into the machines.  hear is the jstack log

FlameGraph are excellent for visualizing performance bottlenecks and hotspots in application profiling but are not designed to pinpoint the exact lines of code where thread deadlocks occur.

Perhaps we could enhance the Thread Dump feature to display thread deadlocks, similar to what the jstack command provides.