[
https://issues.apache.org/jira/browse/FLINK-32700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17748783#comment-17748783
]
Gyula Fora commented on FLINK-32700:
------------------------------------
Don’t get me wrong I think adding support for draining makes perfect sense and
we should start with that:)
In a separate ticket we can discuss the savepoint timeout behavior . It sounds
a little strange that you want to drain pipelines to avoid losing data but you
would be ok with losing data on a savepoint timeout . I think if the job
started to fail we should simply cancel/delete I agree there is a related
ticket somewhere I will try to dig it out after I come back from vacation on
Wednesday.
> Support job drain for Savepoint upgrade mode jobs in Flink Operator
> -------------------------------------------------------------------
>
> Key: FLINK-32700
> URL: https://issues.apache.org/jira/browse/FLINK-32700
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.5.0
> Reporter: Manan Mangal
> Assignee: Manan Mangal
> Priority: Major
>
> During cancel job with savepoint upgrade mode, jobs can be allowed to drain
> by advancing the watermark to the end, before they are stopped, so that the
> in-flight data is not lost.
> If the job fails to drain and hits timeout or any other error, it can be
> cancelled without taking a savepoint.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
