You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/03/28 11:31:00 UTC
[jira] [Closed] (FLINK-26881) Stop with savepoint should pick up the targetDirectory from Flink configuration
[ https://issues.apache.org/jira/browse/FLINK-26881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gyula Fora closed FLINK-26881.
------------------------------
Fix Version/s: kubernetes-operator-1.0.0
Resolution: Fixed
fixed via 97c675ef4f3b57953d5306322136c34111c8cb2f
> Stop with savepoint should pick up the targetDirectory from Flink configuration
> -------------------------------------------------------------------------------
>
> Key: FLINK-26881
> URL: https://issues.apache.org/jira/browse/FLINK-26881
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Reporter: Yang Wang
> Assignee: Yang Wang
> Priority: Blocker
> Labels: pull-request-available
> Fix For: kubernetes-operator-0.1.0, kubernetes-operator-1.0.0
>
>
> Upgrading stateless FlinkDeployment to savepoint still could not work. Because {{FlinkService#cancelJob}} does not pick up the target directory in the flink configuration.
>
> {code:java}
> case SAVEPOINT:
> String savepoint =
> clusterClient
> .stopWithSavepoint(jobID, false, null)
> .get(1, TimeUnit.MINUTES); {code}
> We should use configured savepoint directory instead of {{null}} in the above implementation.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)