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/07/15 06:43:00 UTC

[jira] [Updated] (FLINK-27273) Support both configMap and zookeeper based HA data clean up

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

Gyula Fora updated FLINK-27273:
-------------------------------
    Fix Version/s: kubernetes-operator-1.2.0
                       (was: kubernetes-operator-1.1.0)

> Support both configMap and zookeeper based HA data clean up
> -----------------------------------------------------------
>
>                 Key: FLINK-27273
>                 URL: https://issues.apache.org/jira/browse/FLINK-27273
>             Project: Flink
>          Issue Type: Improvement
>          Components: Kubernetes Operator
>            Reporter: Aitozi
>            Priority: Major
>             Fix For: kubernetes-operator-1.2.0
>
>
> As discussed in [comments|https://github.com/apache/flink-kubernetes-operator/pull/28#discussion_r815695041]
> We only support clean up the ha data based configMap. Considering that zookeeper is still widely used as ha service when deploy on the kubernetes, I think we should still take it into account, otherwise, It will come up with some unexpected behavior when play with zk ha jobs. For example, it will recover old JobGraph when redeploy the application.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)