@Matt Clarke - I do not want to go back and forth with you, but my experiences with NiFi clusters have been slightly different than yours. I am in charge large clusters that run that have nodes on separate hosts (32+ nodes). Based on my experiences, I have had many challenges getting all of the nodes to form a cluster with all nodes. My suggestions might be more of a safest approach rather than the conventional method of adding a new node. ... View more

@Matt Clarke - you correct about adding the node that way. I play it safe by stopping all processors for my data flows, stopping all of the nodes in my cluster, adding the new node as an entry to the authorizers.xml file, copying the flow.xml.gz file to the conf directory of the new node, and deleting the users.xml and authorizations.xml files (You can do this if and iff you specify an Initial Admin in the authorizers.xml file). Of course generating a certificate for the new node and adding custom processors to the lib directory will be needed. the setback with doing it this way is that I have to re set all of the policies. A member on my team is currently writing a script that will generate authorizations.xml, users.xml and authorizers.xml files on the fly when we add a new node to save time in the long run. Best, Michael ... View more

Based on my experiences, I stop all data flows, get a clean (unstarted version of nifi), and copy the flow.xml.gz file from NCM into that new instance. Other actions I do include: delete the users.xml and authorizations.xml files on each existing node add the new node as an xml entry in the authorizers.xml file for all nodes including the newly added one. (all nodes should have the same authorizers.xml and zookeeper.properties create certificate for that node when using HTTPS mode add custom processors (nar files) to the lib folder if need be ... View more

I have it installed on my server, and the time on my server is the correct with the correct timezone. ... View more

Thank you @Timothy Spann ! ... View more

@mpayne, I have five zookeeper instances running and they are configured properly in the zookeeper.properties file. I am not using the embedded zookeepers since I am forming a cluster, and using the embedded zookeepers for each node is not allowed. I never designated a root node since the documentation did not require it. Should I be doing this? I will look into ensuring that all nodes can communicate with all zookeepers. Thank you for the advice! ... View more

@Timothy Spann I did all of these and configured the state-management.xml, zookeeper.properties, nifi.properties, and authorizers.xml files. After much experimentation, I got all five nodes to cluster, and here is what I did from a high level. 1. Get two nodes to cluster 2. For every node thereafter, start and restart each node until the node "joins" the cluster It can be time consuming but it worked. ... View more

Hi @Timothy Spann I have set these values that you mentioned, and even updated the zookeeper.properties, state-management.xml , and authorizers.xml files with the appropriate node/port information, but the clustering now goes two sets of two nodes and then one node that does not form a cluster. Best, Michael ... View more