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/04/29 05:37:00 UTC

[jira] [Commented] (FLINK-27435) Kubernetes Operator keeps savepoint history

    [ https://issues.apache.org/jira/browse/FLINK-27435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529778#comment-17529778 ] 

Gyula Fora commented on FLINK-27435:
------------------------------------

Do you think we should add this to the status or introduce a new Savepoint CR similar to how the Ververica platform handles this?

> Kubernetes Operator keeps savepoint history
> -------------------------------------------
>
>                 Key: FLINK-27435
>                 URL: https://issues.apache.org/jira/browse/FLINK-27435
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Thomas Weise
>            Priority: Major
>
> Currently the operator keeps track of the most recent savepoint that was triggered through savepointTriggerNonce. In some cases it is necessary to find older savepoints. For that, it would be nice if the operator can optionally maintain a savepoint history (and perhaps also trigger disposal of savepoints that fall out of the history). The maximum number of savepoints retained could be configured by cound and/or age.
>  



--
This message was sent by Atlassian Jira
(v8.20.7#820007)