[
https://issues.apache.org/jira/browse/FLINK-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eron Wright updated FLINK-7472:
--------------------------------
Description:
When a task manager is no longer needed (e.g. due to idle timeout in slot
manager), the RM should gracefully stop it without spurious warnings. This
implies some actions should be taken before the TM is actually killed.
Proactive steps include stopping the heartbeat monitor and sending a disconnect
message.
It is unclear whether `RM::closeTaskManagerConnection` method should be called
proactively (when we plan to kill a TM), reactively (after the TM is killed),
or both.
was:
When a task manager is no longer needed (e.g. due to idle timeout in slot
manager), the RM should gracefully stop it without spurious warnings. While
implies some actions should be taken before the TM is actually killed.
Proactive steps include stopping the heartbeat monitor and sending a disconnect
message.
It is unclear whether `RM::closeTaskManagerConnection` method should be called
proactively (when we plan to kill a TM), reactively (after the TM is killed),
or both.
> Release task managers gracefully
> --------------------------------
>
> Key: FLINK-7472
> URL: https://issues.apache.org/jira/browse/FLINK-7472
> Project: Flink
> Issue Type: Sub-task
> Components: Cluster Management
> Reporter: Eron Wright
>
> When a task manager is no longer needed (e.g. due to idle timeout in slot
> manager), the RM should gracefully stop it without spurious warnings. This
> implies some actions should be taken before the TM is actually killed.
> Proactive steps include stopping the heartbeat monitor and sending a
> disconnect message.
> It is unclear whether `RM::closeTaskManagerConnection` method should be
> called proactively (when we plan to kill a TM), reactively (after the TM is
> killed), or both.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
