[
https://issues.apache.org/jira/browse/FLINK-32867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17754170#comment-17754170
]
Gyula Fora commented on FLINK-32867:
------------------------------------
If you change the restartNonce a full job restart / upgrade will be performed.
If you have savepoint upgradeMode this will trigger a shutdown with savepoint ,
then restart the job from the savepoint. Sounds like normal behaviour to me
> Suspending job and triggering savepoint when only updating restartNonce
> -----------------------------------------------------------------------
>
> Key: FLINK-32867
> URL: https://issues.apache.org/jira/browse/FLINK-32867
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.4.0
> Reporter: haiqingchen
> Priority: Minor
>
> When I tried to restart Flink Deployment without any configuration change,
> I updated restartNonce to current time mills.
> However, kubernetes operator suspend the Flink Deployment and trigger a
> savepoint but we didn't update savepointTriggerNonce column.
> It's not what we expected as we thought if we didn't update
> savepointTriggerNonce it would never trigger savepoint.
> Is there any possibility to add a precheck(if savepointTriggerNonce is
> updated) when canceling the job?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
