You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/06/10 15:22:00 UTC

[jira] [Updated] (FLINK-27954) JobVertexFlameGraphHandler does not work on standby Dispatcher

     [ https://issues.apache.org/jira/browse/FLINK-27954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler updated FLINK-27954:
-------------------------------------
    Description: 
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.

  was:
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 connectors to the task executors.


> 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
>            Priority: Major
>             Fix For: 1.16.0, 1.15.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.7#820007)