Tan Luu created NIFI-10481:
------------------------------
Summary: NiFi cannot connect to zookeeper on Kubernetes once all
zookeeper pods restarted
Key: NIFI-10481
URL: https://issues.apache.org/jira/browse/NIFI-10481
Project: Apache NiFi
Issue Type: Bug
Components: Configuration
Affects Versions: 1.17.0
Reporter: Tan Luu
Assignee: Tan Luu
When NiFi runs with zookeeper (ZK) deployed in the same Kubernetes cluster, it
cannot connect to ZK once all ZK pods get restarted. The root cause is NiFi
uses Curator Framework with default ensembleTracker enabled so the NiFI
zookeeper client resolves the ZK connection string (eg.
zookeeper.test.svc.cluster.local) to IP addresses and then when all ZK pods get
restarted, NiFi cannot connect to ZK cluster cause pod IP changed when it is
restarted in Kubernetes.
The solution is to add a NiFi configuration option
"nifi.zookeeper.client.ensembleTracker" to enable/disable NiFi zookeeper client
ensembleTracker as mentioned in
https://issues.apache.org/jira/browse/CURATOR-568. Default value is "true" for
backward compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
