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/06/06 12:00:00 UTC

[jira] [Assigned] (FLINK-27913) Remove savepointHistoryMaxCount and savepointHistoryMaxAge from FlinkOperatorConfiguration

     [ https://issues.apache.org/jira/browse/FLINK-27913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gyula Fora reassigned FLINK-27913:
----------------------------------

    Assignee: Nicholas Jiang

> Remove savepointHistoryMaxCount and savepointHistoryMaxAge from FlinkOperatorConfiguration
> ------------------------------------------------------------------------------------------
>
>                 Key: FLINK-27913
>                 URL: https://issues.apache.org/jira/browse/FLINK-27913
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Nicholas Jiang
>            Priority: Critical
>              Labels: Starter
>             Fix For: kubernetes-operator-1.1.0
>
>
> Currently savepointHistoryMaxCount and savepointHistoryMaxAge is part of the FlinkOperatorConfiguration class which means that users cannot override this from their user deployment.
> We should remove it and get it directly from the effective config. 
> We should however introduce a max allowed value for these configurations that is configured on the FlinkOperatorConfiguration level so that users cannot infinitely grow the status size and cause problems for the k8s api.



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