[
https://issues.apache.org/jira/browse/FLINK-27954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-27954:
-----------------------------------
Labels: pull-request-available stale-assigned (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> JobVertexFlameGraphHandler does not work on standby Dispatcher
> --------------------------------------------------------------
>
> Key: FLINK-27954
> URL: https://issues.apache.org/jira/browse/FLINK-27954
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination, Runtime / REST
> Affects Versions: 1.15.0
> Reporter: Chesnay Schepler
> Assignee: Weijie Guo
> Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.18.0, 1.16.3, 1.17.2
>
>
> The {{JobVertexFlameGraphHandler}} relies internally on the
> {{JobVertexThreadInfoTracker}} which calls
> {{ResourceManagerGateway#requestTaskExecutorThreadInfoGateway}} to get a
> gateway for requesting the thread info from the task executors. Since this
> gateway is not serializable it would categorically fail if called from a
> standby dispatcher.
> Instead this should follow the logic of the {{MetricFetcherImpl}}, which
> requests addresses instead and manually connects to the task executors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
