[ https://issues.apache.org/jira/browse/FLINK-35160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
elon_X updated FLINK-35160: --------------------------- Attachment: (was: image-2024-04-18-21-00-04-532.png) > Support for Thread Dump provides a convenient way to display issues of thread > deadlocks in tasks > ------------------------------------------------------------------------------------------------ > > Key: FLINK-35160 > URL: https://issues.apache.org/jira/browse/FLINK-35160 > Project: Flink > Issue Type: Improvement > Components: Runtime / REST > Affects Versions: 1.16.0, 1.17.1, 1.19.0, 1.18.1 > Reporter: elon_X > Priority: Major > Attachments: image-2024-04-18-20-57-52-440.png, > image-2024-04-18-20-58-09-872.png, image-2024-04-18-21-01-22-881.png, > image-2024-04-18-21-34-41-014.png, image-2024-04-20-14-43-36-939.png > > > 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 > !image-2024-04-18-20-57-52-440.png! > !image-2024-04-18-20-58-09-872.png! > 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 > !image-2024-04-18-21-00-04-532.png! > 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. > !image-2024-04-18-21-01-22-881.png! > Perhaps we could enhance the Thread Dump feature to display thread deadlocks, > similar to what the {{jstack}} command provides. > > !image-2024-04-18-21-34-41-014.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)