[jira] [Commented] (FLINK-30813) Residual zk data when using the kubernetes session mode

["Yang Wang (Jira)" <ji...@apache.org>]

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

Yang Wang commented on FLINK-30813:
-----------------------------------

This might be a duplicate of FLINK-20219.

> Residual zk data when using the kubernetes session mode
> -------------------------------------------------------
>
>                 Key: FLINK-30813
>                 URL: https://issues.apache.org/jira/browse/FLINK-30813
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Kubernetes
>            Reporter: liuzhuo
>            Priority: Minor
>
>     If we use kubernetes session mode and use Zookeeper(ZK) as the HA service, the HA data on ZK is not cleared after the session stops.
>     Because  when deleting a session, only call this method:
> {code:java}
> kubernetesClusterDescriptor.killCluster(clusterId);
> {code}
>     However, this method only deletes the deployment associated with the clusterId. If ZK is used as the HA service, data on ZK will be left over when the HA stops, resulting in more and more data on zk.
>  
> Maybe we need to add
> {code:java}
> ClusterClient#shutDownCluster(){code}
> or
> {code:java}
> HighAvailabilityServices#closeAndCleanupAllData(){code}
> When using session mode (native kubernetes)



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