You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/12/06 16:23:00 UTC
[jira] [Updated] (FLINK-33763) Support manual savepoint redeploy for jobs and deployments
[ https://issues.apache.org/jira/browse/FLINK-33763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-33763:
-----------------------------------
Labels: pull-request-available (was: )
> Support manual savepoint redeploy for jobs and deployments
> ----------------------------------------------------------
>
> Key: FLINK-33763
> URL: https://issues.apache.org/jira/browse/FLINK-33763
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Assignee: Gyula Fora
> Priority: Major
> Labels: pull-request-available
>
> A common request is to support a streamlined, user friendly way of redeploying from a target savepoint.
> Previously this was only possible by deleting the CR and recreating it with initialSavepointPath. A big downside of this approach is a loss of savepoint/checkpoint history in the status that some platforms may need, resulting in non-cleaned up save points etc.
> We suggest to introduce a `savepointRedeployNonce` field in the job spec similar to other action trigger nonces.
> If the nonce changes to a new non null value the job will be redeployed from the path specified in the initialSavepointPath (or empty state If the path is empty)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)