Fei Feng created FLINK-35123:
--------------------------------
Summary: Flink Kubernetes Operator should not do deleteHAData
Key: FLINK-35123
URL: https://issues.apache.org/jira/browse/FLINK-35123
Project: Flink
Issue Type: Technical Debt
Components: Kubernetes Operator
Affects Versions: kubernetes-operator-1.8.0, kubernetes-operator-1.7.0
Reporter: Fei Feng
Attachments: image-2024-04-16-15-56-33-426.png
we use flink HA based on zookeeper. when a lots of FlinkDeployment was
deleting, operator will be spend to many time in cleanHaData. the jstack show
that reconcile thread was hang on disconnect with zookeeper. this made deleting
flinkdeployment was slowly.
!image-2024-04-16-15-56-33-426.png|width=502,height=263!
I don't understand why flink kubernetes operator need cleanHAdata , as
[~aitozi] comment in PR [FLINK-26336 Call cancel on deletion & clean up
configmaps as well
#28|https://github.com/apache/flink-kubernetes-operator/pull/28#discussion_r815968841]
{quote}it's a bit of out of scope of the operator responsibility or ability
{quote}
and I'm totally agree with his point.
and I want to know why we call don't call RestClusterClient#shutDownCluster
interface, which is
1. more graceful and reasonable (operator need not care whether flink app
enable ha or not) 2. compatible across flink versions .
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
