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

Xintong Song updated FLINK-23849:
---------------------------------
    Affects Version/s:     (was: 1.13.2)
                           (was: 1.13.1)
                           (was: 1.12.2)

> 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
>
>
> 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.3.4#803005)

Reply via email to