[
https://issues.apache.org/jira/browse/FLINK-13550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17447820#comment-17447820
]
David Morávek commented on FLINK-13550:
---------------------------------------
[~jackylau] that's the line number. It's always -2 for the native methods. See
StackTraceElement [1] for more details. Please use our dedicated user mailing
list [2] for this type of questions, it's more convenient for us to help you
there.
[1] [https://docs.oracle.com/javase/8/docs/api/java/lang/StackTraceElement.html]
[2] [https://flink.apache.org/community.html#mailing-lists]
> Support for CPU FlameGraphs in web UI
> -------------------------------------
>
> Key: FLINK-13550
> URL: https://issues.apache.org/jira/browse/FLINK-13550
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / REST, Runtime / Web Frontend
> Reporter: David Morávek
> Assignee: Alexander Fedulov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.13.0
>
> Attachments: image-2021-11-23-13-36-03-269.png
>
>
> For a better insight into a running job, it would be useful to have ability
> to render a CPU flame graph for a particular job vertex.
> Flink already has a stack-trace sampling mechanism in-place, so it should be
> straightforward to implement.
> This should be done by implementing a new endpoint in REST API, which would
> sample the stack-trace the same way as current BackPressureTracker does, only
> with a different sampling rate and length of sampling.
> [Here|https://www.youtube.com/watch?v=GUNDehj9z9o] is a little demo of the
> feature.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
