You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Zhanghao Chen (Jira)" <ji...@apache.org> on 2022/06/13 23:50:00 UTC

[jira] [Commented] (FLINK-25087) Move heartbeats from akka to the dedicated thread pool in JM

    [ https://issues.apache.org/jira/browse/FLINK-25087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553830#comment-17553830 ] 

Zhanghao Chen commented on FLINK-25087:
---------------------------------------

[~zjureel] Since MainThreadExecutor#schedule, which is used to schedule tasks by HeartBeatManager as well as some other checkers like PhysicalSlotRequestBulkCheckerImpl, are switched to use a dedicated internal scheduled thread pool instead of Akka thread pool in https://github.com/apache/flink/pull/18007, this ticket and https://issues.apache.org/jira/browse/FLINK-25086 should no longer be needed and can be closed. WDYT?

> Move heartbeats from akka to the dedicated thread pool in JM
> ------------------------------------------------------------
>
>                 Key: FLINK-25087
>                 URL: https://issues.apache.org/jira/browse/FLINK-25087
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Runtime / Coordination
>    Affects Versions: 1.14.0, 1.12.5, 1.13.3
>            Reporter: Shammon
>            Assignee: Zhanghao Chen
>            Priority: Major
>
> There're heartbeats in jm, such as heartbeat between jm and tm, jm and rm. These heartbeats are scheduled in akka thread pool. They should be moved to the dedicated thread pool in jm, and job remove them when jm reaches termination.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)