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

ASF GitHub Bot updated FLINK-35414:
-----------------------------------
    Labels: pull-request-available  (was: )

> Cancel jobs through rest api for last-state upgrades
> ----------------------------------------------------
>
>                 Key: FLINK-35414
>                 URL: https://issues.apache.org/jira/browse/FLINK-35414
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Major
>              Labels: pull-request-available
>
> The kubernetes operator currently always deletes the JM deployment directly 
> during last-state upgrades instead of attempting any type of graceful 
> shutdown.
> We could improve the last-state upgrade logic to cancel the job in cases 
> where the JM is healthy and then simply extract the last checkpoint info 
> through the rest api like we already do for terminal job states.
> This would allow the last-state upgrade mode to work even for session jobs 
> and this may even eliminate a few corner cases that can result from the 
> current forceful upgrade mechanism. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to