@Sush217 First thing i noticed here is that it appears that your are trying to start all three NiFi nodes on a single Windows machine. Why? You just add overhead with three NiFi nodes on one server. Typical NiFi cluster setups are one NiFi instance per server. The NiFi properties file would need to be unique per each NiFi instance. They cannot share any binding ports in common since only one node is going to be able to bind to a given port number. This includes properties like: nifi.remote.input.socket.port=
nifi.web.http.port= or nifi.web.https.port= (if secured)
nifi.cluster.node.protocol.port= the configured NiFi hostname also needs to be resolvable. You are using node1, node2, and node3. Since all your NiFI nodes are running on the same Windows server, those would all need to be resolvable to the Windows server IP or you could use same hostname for all three instance since they are running on the same host. Now you are also trying to use the embedded zookeeper which means each instance us going to try to standup and start its own zookeeper node. So just like NiFi, these zookeeper nodes can not share the same port numbers. So each cannot be configured to use 2181, 2888, and 3888. Plus, just like NiFi, the hostnames node1, node 2, and node 3 would all need to be resolvable in DNS or the windows local hosts file. Also not ideal to have multiple zookeeper nodes running on the same server. If you looking to just play around with NiFi, you should just install a standalone instance of NiFi, or setup a single node cluster. You can always add additional nodes to your 1 node cluster later by setting up additional servers with NiFi. As you have it configured currently, my guess here is that if you parse through the nifi-app.log for each of your nodes, you are going to see errors related to resolving each your node hostnames to IPs and then later see address already in use errors. Hope this helps, Matt
... View more
