[
https://issues.apache.org/jira/browse/FLINK-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893897#comment-16893897
]
Gary Yao commented on FLINK-13384:
----------------------------------
Currently, we sample the stacktrace in
[TaskStackTraceSampleableTaskAdapter|https://github.com/apache/flink/blob/bb82aacf46565968359f5ee6d2503c3293d71d6e/flink-runtime/src/main/java/org/apache/flink/runtime/taskexecutor/TaskStackTraceSampleableTaskAdapter.java#L50].
As a quick fix, I see the following options:
* We could somehow expose the {{LegacySourceFunctionThread}} instance from
{{Task}} so that we sample the correct thread in
{{TaskStackTraceSampleableTaskAdapter}}.
* Using
[ThreadGroup|https://docs.oracle.com/javase/7/docs/api/java/lang/ThreadGroup.html],
we could enumerate (all) threads in the JVM and find the correct thread to
sample from.
Maybe [~pnowojski] can chime in here.
> The back pressure monitoring does not work for StreamSources
> ------------------------------------------------------------
>
> Key: FLINK-13384
> URL: https://issues.apache.org/jira/browse/FLINK-13384
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Metrics, Runtime / Task
> Affects Versions: 1.9.0
> Reporter: Dawid Wysakowicz
> Assignee: Gary Yao
> Priority: Blocker
> Fix For: 1.9.0
>
>
> I think it is caused by: [FLINK-12483]. The reason is that the
> {{BackPressureStatsTrackerImpl}} samples only the main thread. FLINK-12483
> introduced a separate thread for executing the sources in the mailbox model.
> It is similar to other old bug that concerned only Kafka source: [FLINK-3456]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
