[
https://issues.apache.org/jira/browse/FLINK-29609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626053#comment-17626053
]
Sriram Ganesh edited comment on FLINK-29609 at 10/29/22 1:34 PM:
-----------------------------------------------------------------
Please don't reassign to others for sometime unless it is immediately required.
I am spending time on this to find a better solution.
was (Author: sriramgr):
Please don't reassign to others for sometime unless it is urgent. I am spending
time on this to find a better solution.
> Clean up jobmanager deployment on suspend after recording savepoint info
> ------------------------------------------------------------------------
>
> Key: FLINK-29609
> URL: https://issues.apache.org/jira/browse/FLINK-29609
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Sriram Ganesh
> Priority: Major
> Fix For: kubernetes-operator-1.3.0
>
>
> Currently in case of suspending with savepoint. The jobmanager pod will
> linger there forever after cancelling the job.
> This is currently used to ensure consistency in case the
> operator/cancel-with-savepoint operation fails.
> Once we are sure however that the savepoint has been recorded and the job is
> shut down, we should clean up all the resources. Optionally we can make this
> configurable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
