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

Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2022/04/13 06:28:06 UTC

[jira] [Updated] (FLINK-23849) Support react to the node decommissioning change state on yarn and do graceful restart

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

Yun Gao updated FLINK-23849:
----------------------------
    Fix Version/s: 1.16.0

> Support react to the node decommissioning change state on yarn and do graceful restart
> --------------------------------------------------------------------------------------
>
>                 Key: FLINK-23849
>                 URL: https://issues.apache.org/jira/browse/FLINK-23849
>             Project: Flink
>          Issue Type: New Feature
>          Components: Deployment / YARN
>            Reporter: zlzhang0122
>            Priority: Major
>             Fix For: 1.15.0, 1.16.0
>
>
> Now we are not interested in node updates in YarnContainerEventHandler.onNodesUpdated , but sometimes we want to evict the running flink process on one node and graceful restart on the other node because of some unexpected reason such as the physical machine need to be recycle or the cloud computing cluster need to be migration. Thus, we can react to the node decommissioning change state, and call the stopWithSavepoint function and then restart it.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)