Clay, Not sure what problem you are trying to solve by copying the flow file around. I am assuming you want to deploy a Flow to a NiFi cluster? If so, we use NiFi CLI (part of the NiFi toolkit) + NiFi Registry to copy flows to a node or cluster.
https://pierrevillard.com/2018/04/09/automate-workflow-deployment-in-apache-nifi-with-the-nifi-registry/ https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html 1 commandline call and it copies the flow from the NiFi registry (bucket + flowname) and deploys it to any of our NiFi systems. You can even have 10 independent instances of NiFi running and use the toolkit to create an ephemeral job by copying the flow to said instance of your choice, running it, and deleting it. A 16 core/48GB Ram NiFi instance can do a lot of work in its own without the need for a cluster setup. Erik Anderson Bloomberg On Wed, Jul 24, 2019, at 5:50 AM, Clay Teahouse wrote: > Hi Everyone, > I have a cluster of multiple nodes. If I place flow.xml on all of them before > starting the nodes, would that cause a conflict? If yes, can I disable > syncing between the nodes? I do not want to have to decide on a primary node > at the start up. > In other words, can the primary node be decided on the run time? > > thank you > Clay.
