You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Jean-Sebastien Vachon <js...@brizodata.com> on 2018/07/09 15:47:38 UTC
Problem with embedded Zookeeper
Hi all,
I am following this guide (https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/) in order to setup a Nifi cluster containing 3 nodes for testing purposes. The three nodes are up and running but somehow, they are not in cluster.
I've checked my configs over and over and can not figure out why they are not clustered. Here are portions of my configuration file.
nifi.state.management.embedded.zookeeper.start=true
nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties
nifi.cluster.is.node=true
nifi.cluster.node.address=nifi02.brizo.com
nifi.cluster.node.protocol.port=9999
nifi.zookeeper.connect.string=nifi01.brizo.com:2181,nifi02.brizo.com:2181,nifi03.brizo.com:2181
nifi.remote.input.host=nifi02.brizo.com
nifi.remote.input.secure=false
nifi.remote.input.socket.port=9998
I've created the myid file under $NIFI_HOME/state/zookeeper for each of the nodes.
When I start a node and check the logs (I raised the level to DEBUG), I can see very little content referring to Zookeeper. I also tried to telnet port 2181 and nothing is listening on that port.
I am obviously missing something. Any idea what it could be?
Thanks
--
Jean-Sébastien Vachon
téléphone: (418) 655-6661
vachonjs@gmail.com<ma...@brizodata.com>
jsvachon@brizodata.com<ma...@brizodata.com>
www.brizodata.com<http://www.brizodata.com/>
Re: Problem with embedded Zookeeper
Posted by Andy LoPresto <al...@apache.org>.
You can tighten the election wait time and the max number of expected nodes in nifi.properties to vastly shorten that wait. I should have mentioned that earlier. It’s set for those defaults with the expectation of dynamically sized clusters and network latency on bringing machines online.
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jul 9, 2018, at 11:18 AM, Jean-Sebastien Vachon <js...@brizodata.com> wrote:
>
> I finally managed to get it up and running but it required a few additional steps.
>
> First, I had a few permissions /ownership that were causing issues. I had to make a few changes so that the ‘nifi’ user was the owner of everything. This was most likely the main cause of all my issues.
>
> Then, when I started all three nodes at the same time.. they were taking forever to establish the election mechanism.
> They were all saying “still voting on which Flow is the correct flow for the cluster”. I stopped everything and restarted only one node… after some time, it came up fine and then I started the two other nodes and they were finally able to join the cluster.
>
> I am not sure if this was the correct way of bringing up everything but I can finally proceed with my tests
>
> Thanks all
>
> From: Andy LoPresto <al...@apache.org>
> Sent: July 9, 2018 1:42 PM
> To: users@nifi.apache.org
> Subject: Re: Problem with embedded Zookeeper
>
> You should not have to modify the state-management.xml file. Here is an example of cluster configuration (the certificates here use wildcard CNs, which is an active issue I’m working to resolve, but the ZK settings are all correct). I am currently running this cluster using embedded ZK on 3 NiFi instances running on the same local machine. You’ll have to change the DNS entries to your nodes.
>
> https://github.com/alopresto/nifi_secure_cluster_wildcard <https://github.com/alopresto/nifi_secure_cluster_wildcard>
>
> Andy LoPresto
> alopresto@apache.org <ma...@apache.org>
> alopresto.apache@gmail.com <ma...@gmail.com>
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Jul 9, 2018, at 10:07 AM, Jean-Sebastien Vachon <jsvachon@brizodata.com <ma...@brizodata.com>> wrote:
>
> Hi Andy,
>
> Thanks for the suggestion but I did spot that typo earlier. One quick question, do we need to make any change to the state-management.xml file? Like filling the “Connect String” property to something like:
>
> <cluster-provider>
> <id>zk-provider</id>
> <class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class>
> <property name="Connect String">nifi01.brizo.com <http://nifi01.brizo.com/>:2181,nifi02.brizo.com <http://nifi02.brizo.com/>:2181,nifi03.brizo.com <http://nifi03.brizo.com/>:2181</property>
> <property name="Root Node">/nifi</property>
> <property name="Session Timeout">10 seconds</property>
> <property name="Access Control">Open</property>
> </cluster-provider>
>
> Actually, I tried this and it didn’t help 😉
>
> I might have to try without the Embedded ZK like someone else suggested but I don’t see any reason why the embedded version would not work
>
> Thanks
>
> From: Andy LoPresto <alopresto@apache.org <ma...@apache.org>>
> Sent: July 9, 2018 12:29 PM
> To: users@nifi.apache.org <ma...@nifi.apache.org>
> Subject: Re: Problem with embedded Zookeeper
>
> Jean-Sebastian,
>
> Pierre’s guide has a typo in it — make sure that you configured the Zookeeper nodes with *./conf/zookeeper.properties*, not *./conf/zookeep.properties*. The location of the ZK configuration file needs to match the property defined in nifi.properties as nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties.
>
> I just ran through this the other day and realized there was a typo there. Hopefully this helps. Let us know if you have any other issues.
>
>
> Andy LoPresto
> alopresto@apache.org <ma...@apache.org>
> alopresto.apache@gmail.com <ma...@gmail.com>
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Jul 9, 2018, at 8:47 AM, Jean-Sebastien Vachon <jsvachon@brizodata.com <ma...@brizodata.com>> wrote:
>
> Hi all,
>
> I am following this guide (https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/ <https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/>) in order to setup a Nifi cluster containing 3 nodes for testing purposes. The three nodes are up and running but somehow, they are not in cluster.
>
> I’ve checked my configs over and over and can not figure out why they are not clustered. Here are portions of my configuration file.
>
> nifi.state.management.embedded.zookeeper.start=true
> nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties
>
> nifi.cluster.is.node=true
> nifi.cluster.node.address=nifi02.brizo.com <http://nifi02.brizo.com/>
> nifi.cluster.node.protocol.port=9999
>
> nifi.zookeeper.connect.string=nifi01.brizo.com <http://nifi01.brizo.com/>:2181,nifi02.brizo.com <http://nifi02.brizo.com/>:2181,nifi03.brizo.com <http://nifi03.brizo.com/>:2181
> nifi.remote.input.host=nifi02.brizo.com <http://nifi02.brizo.com/>
> nifi.remote.input.secure=false
> nifi.remote.input.socket.port=9998
>
> I’ve created the myid file under $NIFI_HOME/state/zookeeper for each of the nodes.
>
> When I start a node and check the logs (I raised the level to DEBUG), I can see very little content referring to Zookeeper. I also tried to telnet port 2181 and nothing is listening on that port.
>
> I am obviously missing something. Any idea what it could be?
>
> Thanks
> --
> Jean-Sébastien Vachon
>
> téléphone: (418) 655-6661
> vachonjs@gmail.com <ma...@brizodata.com>
> jsvachon@brizodata.com <ma...@brizodata.com>
> www.brizodata.com <http://www.brizodata.com/>
RE: Problem with embedded Zookeeper
Posted by Jean-Sebastien Vachon <js...@brizodata.com>.
I finally managed to get it up and running but it required a few additional steps.
First, I had a few permissions /ownership that were causing issues. I had to make a few changes so that the ‘nifi’ user was the owner of everything. This was most likely the main cause of all my issues.
Then, when I started all three nodes at the same time.. they were taking forever to establish the election mechanism.
They were all saying “still voting on which Flow is the correct flow for the cluster”. I stopped everything and restarted only one node… after some time, it came up fine and then I started the two other nodes and they were finally able to join the cluster.
I am not sure if this was the correct way of bringing up everything but I can finally proceed with my tests
Thanks all
From: Andy LoPresto <al...@apache.org>
Sent: July 9, 2018 1:42 PM
To: users@nifi.apache.org
Subject: Re: Problem with embedded Zookeeper
You should not have to modify the state-management.xml file. Here is an example of cluster configuration (the certificates here use wildcard CNs, which is an active issue I’m working to resolve, but the ZK settings are all correct). I am currently running this cluster using embedded ZK on 3 NiFi instances running on the same local machine. You’ll have to change the DNS entries to your nodes.
https://github.com/alopresto/nifi_secure_cluster_wildcard
Andy LoPresto
alopresto@apache.org<ma...@apache.org>
alopresto.apache@gmail.com<ma...@gmail.com>
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
On Jul 9, 2018, at 10:07 AM, Jean-Sebastien Vachon <js...@brizodata.com>> wrote:
Hi Andy,
Thanks for the suggestion but I did spot that typo earlier. One quick question, do we need to make any change to the state-management.xml file? Like filling the “Connect String” property to something like:
<cluster-provider>
<id>zk-provider</id>
<class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class>
<property name="Connect String">nifi01.brizo.com<http://nifi01.brizo.com/>:2181,nifi02.brizo.com<http://nifi02.brizo.com/>:2181,nifi03.brizo.com<http://nifi03.brizo.com/>:2181</property>
<property name="Root Node">/nifi</property>
<property name="Session Timeout">10 seconds</property>
<property name="Access Control">Open</property>
</cluster-provider>
Actually, I tried this and it didn’t help 😉
I might have to try without the Embedded ZK like someone else suggested but I don’t see any reason why the embedded version would not work
Thanks
From: Andy LoPresto <al...@apache.org>>
Sent: July 9, 2018 12:29 PM
To: users@nifi.apache.org<ma...@nifi.apache.org>
Subject: Re: Problem with embedded Zookeeper
Jean-Sebastian,
Pierre’s guide has a typo in it — make sure that you configured the Zookeeper nodes with *./conf/zookeeper.properties*, not *./conf/zookeep.properties*. The location of the ZK configuration file needs to match the property defined in nifi.properties as nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties.
I just ran through this the other day and realized there was a typo there. Hopefully this helps. Let us know if you have any other issues.
Andy LoPresto
alopresto@apache.org<ma...@apache.org>
alopresto.apache@gmail.com<ma...@gmail.com>
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
On Jul 9, 2018, at 8:47 AM, Jean-Sebastien Vachon <js...@brizodata.com>> wrote:
Hi all,
I am following this guide (https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/) in order to setup a Nifi cluster containing 3 nodes for testing purposes. The three nodes are up and running but somehow, they are not in cluster.
I’ve checked my configs over and over and can not figure out why they are not clustered. Here are portions of my configuration file.
nifi.state.management.embedded.zookeeper.start=true
nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties
nifi.cluster.is.node=true
nifi.cluster.node.address=nifi02.brizo.com<http://nifi02.brizo.com/>
nifi.cluster.node.protocol.port=9999
nifi.zookeeper.connect.string=nifi01.brizo.com<http://nifi01.brizo.com/>:2181,nifi02.brizo.com<http://nifi02.brizo.com/>:2181,nifi03.brizo.com<http://nifi03.brizo.com/>:2181
nifi.remote.input.host=nifi02.brizo.com<http://nifi02.brizo.com/>
nifi.remote.input.secure=false
nifi.remote.input.socket.port=9998
I’ve created the myid file under $NIFI_HOME/state/zookeeper for each of the nodes.
When I start a node and check the logs (I raised the level to DEBUG), I can see very little content referring to Zookeeper. I also tried to telnet port 2181 and nothing is listening on that port.
I am obviously missing something. Any idea what it could be?
Thanks
--
Jean-Sébastien Vachon
téléphone: (418) 655-6661
vachonjs@gmail.com<ma...@brizodata.com>
jsvachon@brizodata.com<ma...@brizodata.com>
www.brizodata.com<http://www.brizodata.com/>
Re: Problem with embedded Zookeeper
Posted by Andy LoPresto <al...@apache.org>.
You should not have to modify the state-management.xml file. Here is an example of cluster configuration (the certificates here use wildcard CNs, which is an active issue I’m working to resolve, but the ZK settings are all correct). I am currently running this cluster using embedded ZK on 3 NiFi instances running on the same local machine. You’ll have to change the DNS entries to your nodes.
https://github.com/alopresto/nifi_secure_cluster_wildcard <https://github.com/alopresto/nifi_secure_cluster_wildcard>
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jul 9, 2018, at 10:07 AM, Jean-Sebastien Vachon <js...@brizodata.com> wrote:
>
> Hi Andy,
>
> Thanks for the suggestion but I did spot that typo earlier. One quick question, do we need to make any change to the state-management.xml file? Like filling the “Connect String” property to something like:
>
> <cluster-provider>
> <id>zk-provider</id>
> <class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class>
> <property name="Connect String">nifi01.brizo.com <http://nifi01.brizo.com/>:2181,nifi02.brizo.com <http://nifi02.brizo.com/>:2181,nifi03.brizo.com <http://nifi03.brizo.com/>:2181</property>
> <property name="Root Node">/nifi</property>
> <property name="Session Timeout">10 seconds</property>
> <property name="Access Control">Open</property>
> </cluster-provider>
>
> Actually, I tried this and it didn’t help 😉
>
> I might have to try without the Embedded ZK like someone else suggested but I don’t see any reason why the embedded version would not work
>
> Thanks
>
> From: Andy LoPresto <al...@apache.org>
> Sent: July 9, 2018 12:29 PM
> To: users@nifi.apache.org
> Subject: Re: Problem with embedded Zookeeper
>
> Jean-Sebastian,
>
> Pierre’s guide has a typo in it — make sure that you configured the Zookeeper nodes with *./conf/zookeeper.properties*, not *./conf/zookeep.properties*. The location of the ZK configuration file needs to match the property defined in nifi.properties as nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties.
>
> I just ran through this the other day and realized there was a typo there. Hopefully this helps. Let us know if you have any other issues.
>
>
> Andy LoPresto
> alopresto@apache.org <ma...@apache.org>
> alopresto.apache@gmail.com <ma...@gmail.com>
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> On Jul 9, 2018, at 8:47 AM, Jean-Sebastien Vachon <jsvachon@brizodata.com <ma...@brizodata.com>> wrote:
>
> Hi all,
>
> I am following this guide (https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/ <https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/>) in order to setup a Nifi cluster containing 3 nodes for testing purposes. The three nodes are up and running but somehow, they are not in cluster.
>
> I’ve checked my configs over and over and can not figure out why they are not clustered. Here are portions of my configuration file.
>
> nifi.state.management.embedded.zookeeper.start=true
> nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties
>
> nifi.cluster.is.node=true
> nifi.cluster.node.address=nifi02.brizo.com <http://nifi02.brizo.com/>
> nifi.cluster.node.protocol.port=9999
>
> nifi.zookeeper.connect.string=nifi01.brizo.com <http://nifi01.brizo.com/>:2181,nifi02.brizo.com <http://nifi02.brizo.com/>:2181,nifi03.brizo.com <http://nifi03.brizo.com/>:2181
> nifi.remote.input.host=nifi02.brizo.com <http://nifi02.brizo.com/>
> nifi.remote.input.secure=false
> nifi.remote.input.socket.port=9998
>
> I’ve created the myid file under $NIFI_HOME/state/zookeeper for each of the nodes.
>
> When I start a node and check the logs (I raised the level to DEBUG), I can see very little content referring to Zookeeper. I also tried to telnet port 2181 and nothing is listening on that port.
>
> I am obviously missing something. Any idea what it could be?
>
> Thanks
> --
> Jean-Sébastien Vachon
>
> téléphone: (418) 655-6661
> vachonjs@gmail.com <ma...@brizodata.com>
> jsvachon@brizodata.com <ma...@brizodata.com>
> www.brizodata.com <http://www.brizodata.com/>
RE: Problem with embedded Zookeeper
Posted by Jean-Sebastien Vachon <js...@brizodata.com>.
Hi Andy,
Thanks for the suggestion but I did spot that typo earlier. One quick question, do we need to make any change to the state-management.xml file? Like filling the “Connect String” property to something like:
<cluster-provider>
<id>zk-provider</id>
<class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class>
<property name="Connect String">nifi01.brizo.com:2181,nifi02.brizo.com:2181,nifi03.brizo.com:2181</property>
<property name="Root Node">/nifi</property>
<property name="Session Timeout">10 seconds</property>
<property name="Access Control">Open</property>
</cluster-provider>
Actually, I tried this and it didn’t help 😉
I might have to try without the Embedded ZK like someone else suggested but I don’t see any reason why the embedded version would not work
Thanks
From: Andy LoPresto <al...@apache.org>
Sent: July 9, 2018 12:29 PM
To: users@nifi.apache.org
Subject: Re: Problem with embedded Zookeeper
Jean-Sebastian,
Pierre’s guide has a typo in it — make sure that you configured the Zookeeper nodes with *./conf/zookeeper.properties*, not *./conf/zookeep.properties*. The location of the ZK configuration file needs to match the property defined in nifi.properties as nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties.
I just ran through this the other day and realized there was a typo there. Hopefully this helps. Let us know if you have any other issues.
Andy LoPresto
alopresto@apache.org<ma...@apache.org>
alopresto.apache@gmail.com<ma...@gmail.com>
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
On Jul 9, 2018, at 8:47 AM, Jean-Sebastien Vachon <js...@brizodata.com>> wrote:
Hi all,
I am following this guide (https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/) in order to setup a Nifi cluster containing 3 nodes for testing purposes. The three nodes are up and running but somehow, they are not in cluster.
I’ve checked my configs over and over and can not figure out why they are not clustered. Here are portions of my configuration file.
nifi.state.management.embedded.zookeeper.start=true
nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties
nifi.cluster.is.node=true
nifi.cluster.node.address=nifi02.brizo.com<http://nifi02.brizo.com/>
nifi.cluster.node.protocol.port=9999
nifi.zookeeper.connect.string=nifi01.brizo.com<http://nifi01.brizo.com/>:2181,nifi02.brizo.com<http://nifi02.brizo.com/>:2181,nifi03.brizo.com<http://nifi03.brizo.com/>:2181
nifi.remote.input.host=nifi02.brizo.com<http://nifi02.brizo.com/>
nifi.remote.input.secure=false
nifi.remote.input.socket.port=9998
I’ve created the myid file under $NIFI_HOME/state/zookeeper for each of the nodes.
When I start a node and check the logs (I raised the level to DEBUG), I can see very little content referring to Zookeeper. I also tried to telnet port 2181 and nothing is listening on that port.
I am obviously missing something. Any idea what it could be?
Thanks
--
Jean-Sébastien Vachon
téléphone: (418) 655-6661
vachonjs@gmail.com<ma...@brizodata.com>
jsvachon@brizodata.com<ma...@brizodata.com>
www.brizodata.com<http://www.brizodata.com/>
Re: Problem with embedded Zookeeper
Posted by Andy LoPresto <al...@apache.org>.
Jean-Sebastian,
Pierre’s guide has a typo in it — make sure that you configured the Zookeeper nodes with *./conf/zookeeper.properties*, not *./conf/zookeep.properties*. The location of the ZK configuration file needs to match the property defined in nifi.properties as nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties.
I just ran through this the other day and realized there was a typo there. Hopefully this helps. Let us know if you have any other issues.
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jul 9, 2018, at 8:47 AM, Jean-Sebastien Vachon <js...@brizodata.com> wrote:
>
> Hi all,
>
> I am following this guide (https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/ <https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/>) in order to setup a Nifi cluster containing 3 nodes for testing purposes. The three nodes are up and running but somehow, they are not in cluster.
>
> I’ve checked my configs over and over and can not figure out why they are not clustered. Here are portions of my configuration file.
>
> nifi.state.management.embedded.zookeeper.start=true
> nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties
>
> nifi.cluster.is.node=true
> nifi.cluster.node.address=nifi02.brizo.com <http://nifi02.brizo.com/>
> nifi.cluster.node.protocol.port=9999
>
> nifi.zookeeper.connect.string=nifi01.brizo.com <http://nifi01.brizo.com/>:2181,nifi02.brizo.com <http://nifi02.brizo.com/>:2181,nifi03.brizo.com <http://nifi03.brizo.com/>:2181
> nifi.remote.input.host=nifi02.brizo.com <http://nifi02.brizo.com/>
> nifi.remote.input.secure=false
> nifi.remote.input.socket.port=9998
>
> I’ve created the myid file under $NIFI_HOME/state/zookeeper for each of the nodes.
>
> When I start a node and check the logs (I raised the level to DEBUG), I can see very little content referring to Zookeeper. I also tried to telnet port 2181 and nothing is listening on that port.
>
> I am obviously missing something. Any idea what it could be?
>
> Thanks
> --
> Jean-Sébastien Vachon
>
> téléphone: (418) 655-6661
> vachonjs@gmail.com <ma...@brizodata.com>
> jsvachon@brizodata.com <ma...@brizodata.com>
> www.brizodata.com <http://www.brizodata.com/>
Re: Problem with embedded Zookeeper
Posted by Mike Thomsen <mi...@gmail.com>.
I would recommend just setting up a plain vanilla ZooKeeper instead of
using the embedded ones.
On Mon, Jul 9, 2018 at 11:47 AM Jean-Sebastien Vachon <
jsvachon@brizodata.com> wrote:
> Hi all,
>
>
>
> I am following this guide (
> https://pierrevillard.com/2016/08/13/apache-nifi-1-0-0-cluster-setup/) in
> order to setup a Nifi cluster containing 3 nodes for testing purposes. The
> three nodes are up and running but somehow, they are not in cluster.
>
>
>
> I’ve checked my configs over and over and can not figure out why they are
> not clustered. Here are portions of my configuration file.
>
>
>
> nifi.state.management.embedded.zookeeper.start=true
>
>
> nifi.state.management.embedded.zookeeper.properties=./conf/zookeeper.properties
>
>
>
> nifi.cluster.is.node=true
>
> nifi.cluster.node.address=nifi02.brizo.com
>
> nifi.cluster.node.protocol.port=9999
>
>
>
> nifi.zookeeper.connect.string=nifi01.brizo.com:2181,nifi02.brizo.com:2181,
> nifi03.brizo.com:2181
>
> nifi.remote.input.host=nifi02.brizo.com
>
> nifi.remote.input.secure=false
>
> nifi.remote.input.socket.port=9998
>
>
>
> I’ve created the myid file under $NIFI_HOME/state/zookeeper for each of
> the nodes.
>
>
>
> When I start a node and check the logs (I raised the level to DEBUG), I
> can see very little content referring to Zookeeper. I also tried to telnet
> port 2181 and nothing is listening on that port.
>
>
>
> I am obviously missing something. Any idea what it could be?
>
>
>
> Thanks
>
> --
>
> Jean-Sébastien Vachon
>
> téléphone: *(418) 655-6661 <(418)%20655-6661>*
>
> vachonjs@gmail.com <js...@brizodata.com>
>
> jsvachon@brizodata.com
>
> www.brizodata.com
>
>
>