You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/01/09 16:43:00 UTC

[jira] [Commented] (NIFI-10481) Support Disabling ZooKeeper Client Ensemble Tracking

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

ASF subversion and git services commented on NIFI-10481:
--------------------------------------------------------

Commit ea93dec079d13157abd53d09374120eb55481004 in nifi's branch refs/heads/main from nathluu
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ea93dec079 ]

NIFI-10481 Support disabling ZooKeeper Ensemble Tracking

This closes #6400

Signed-off-by: David Handermann <ex...@apache.org>


> Support Disabling ZooKeeper Client Ensemble Tracking
> ----------------------------------------------------
>
>                 Key: NIFI-10481
>                 URL: https://issues.apache.org/jira/browse/NIFI-10481
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 1.17.0
>            Reporter: Tan Luu
>            Assignee: Tan Luu
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> 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)