[
https://issues.apache.org/jira/browse/FLINK-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251688#comment-17251688
]
Chesnay Schepler commented on FLINK-12193:
------------------------------------------
hmm...maybe practical isn't the right word. It is certainly possible; the
heartbeat interval is usually set globally for all processes, and it might be
that a user wants task executors to be cleaned up quickly if they are no longer
needed, but not decrease the heartbeat to the same value since they do quite a
bit more on say the JobManager side.
For example, sending around all the reports about partitions/slots/executions
every few milliseconds should be quite expensive, in contrast the release
timeout check is pretty cheap, since it is ultimately little more than a ping.
> Send TM "can be released status" with RM heartbeat
> --------------------------------------------------
>
> Key: FLINK-12193
> URL: https://issues.apache.org/jira/browse/FLINK-12193
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Reporter: Andrey Zagrebin
> Priority: Major
> Labels: starter
> Fix For: 1.13.0
>
>
> We introduced a conditional release of Task Executor in Resource Manager in
> FLINK-10941. At the moment RM directly asks TE every release timeout whether
> it can be released (all depending consumers are done). We can piggyback TE/RM
> heartbeats for this purpose. In this case, we do not need additional RPC call
> to TE gateway and could potentially release TE quicker.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
