You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Tang (Jira)" <ji...@apache.org> on 2023/04/14 02:44:00 UTC
[jira] [Commented] (FLINK-31795) Add Config to enable/disable savepoint cleanup
[ https://issues.apache.org/jira/browse/FLINK-31795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17712167#comment-17712167 ]
Yun Tang commented on FLINK-31795:
----------------------------------
[~darenwkt] If users want to keep the full savepoint history, why not make the {{savepoint.history.max.count}} unlimited? By doing so, we can avoid to introduce another configuration here.
> Add Config to enable/disable savepoint cleanup
> ----------------------------------------------
>
> Key: FLINK-31795
> URL: https://issues.apache.org/jira/browse/FLINK-31795
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.4.0
> Reporter: Daren Wong
> Priority: Minor
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.4.0
>
>
> Proposed to add config: `KubernetesOperatorConfigOptions.{color:#9876aa}OPERATOR_SAVEPOINT_CLEANER_ENABLED` or {color}
> {color:#6a8759}"savepoint.cleaner.enabled"{color}
>
> {color:#6a8759}This proposal is to give user the flexibility to disable savepoint clean up by SavepointObserver for use cases such as u{color}{color:#6a8759}ser wants to keep full savepoint history.{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)