Member since
02-11-2016
25
Posts
6
Kudos Received
2
Solutions
05-28-2016
05:36 PM
Hello one last time, as follow-up to your last comment: "If the cluster NCM you are joining this node to already has an existing flow or templates, this node will fail to join because they will not match. NO need to reinstall to fix this if that is the case. Simply delete the flow.xml.gz file and the templates directory before starting it again. When it joins the cluster it will get the current flow and templates from the NCM." When the " start" command was originally issued (to accidently make this a standalone configuration) nothing had been configured - there was no NCM or node specific parameters defined. Bottomline: There were no other NiFi configurations previously in existence in this environment. Thanks again for your great answers and the articles you post to this site. They are very much appreciated.
... View more
05-25-2016
10:57 PM
Thank you very, very much for your feedback.
... View more
05-25-2016
10:42 PM
Hello, Thank you for the fast reply. Someone else initially installed the software. A start command was issued via a NiFi Service once, then we realized I needed to go in and edit several of the properties files for this configuration, since it is a Clustered environment. Have we unintentionally caused the configuration to be unusable, or should we reload the software? Now I am trying to go back and edit all of the configuration files like: nifi.properties, bootstrap,zookeeper, authority providers and users... to try and set this up for a cluster environment using embedded zookeeper. Thank you for your reply.
... View more
05-25-2016
10:07 PM
Hi,
Reading the latest NiFi manual from the Hortworks web site: http://docs.hortonworks.com/HDPDocuments/HDF1/HDF-1.2.0.1/bk_AdminGuide/content/index.html (this uses NiFi version 0.6.0.)
The manual talks about creating a 'state' directory you need to use, when you want to use "embedded zookeeper' for a clustered NiFi environment:
When using an embedded ZooKeeper, the ./conf/zookeeper.properties file has a property named dataDir . By default, this value is set to ./state/zookeeper . If more than one NiFi node is running an embedded ZooKeeper, it is important to tell the server which one it is. This is accomplished by creating a file named myid and placing it in ZooKeeper's data directory. The contents of this file should be the index of the server as specific by the server.<number> . So for one of the ZooKeeper servers, we will accomplish this by performing the following commands:
cd $NIFI_HOME
mkdir state
mkdir state/zookeeper
echo 1 > state/zookeeper/myid
When I started looking around the directories, before running these commands from the manual, I found a 'state' directory already in out there in the same directory level as 'conf', 'logs' and 'bin'. The ONLY sub-directory under "state" was" "local".
I don't want to 'assume' anything. Should I use this 'state' directory and build a 'zookeeper' sub directory in it, then add the file called 'myid'? I am logged on as the root user trying to create this.
... View more
Labels:
- Labels:
-
Apache NiFi