You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2022/10/25 03:45:45 UTC

[GitHub] [nifi] nathluu commented on pull request #6400: NIFI-10481 Add NiFi configuration to disable zk client ensembleTracker

nathluu commented on PR #6400:
URL: https://github.com/apache/nifi/pull/6400#issuecomment-1289937025

   Thank @thenatog for helping review and test my PR. To verify the EnsembleTracker option, we need the zookeeper quorum deployed inside the K8S cluster same as with NiFi. Below are the steps for testing:
   Setup:
   - Deploy ZK quorum in the AKS
   - Deploy NiFi to use K8S service FQDN of ZK as the connection string e.g. test-zookeeper.zk-ns.svc.cluster.local:2181
   Case 1: EnsembleTracker enabled (default)
   1/ Rollout restart all ZK pods (Not NiFi pods)
   2/ When all ZK restarted and up again, access the NiFi canvas UI
   3/ Verify that the UI will not be load
   4/ Rollout restart all of the NiFi pods will resolve the issue
   Case 2: EnsembleTracker disable (set **nifi.zookeeper.client.ensembleTracker=false** in nifi.properties file)
   With a working NiFi (canvas is accessible)
   1/ Rollout restart all ZK pods (Not NiFi pods)
   2/ When all ZK restarted and up again, access the NiFi canvas UI
   3/ Verify that the NiFi canvas can be access normally


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org