David I think what is worth further clarifying is the fact that NiFi flow lifecycle is based on lifecycle of individual components (e.g., Processors) within the flow. In other words one can start/stop any Processor individually. So, the ‘autoResumeState’ will not start your flow automatically, it will simply preserve the state of all components between restarts. This means that if any one of those components was stopped it will resume as stopped.
Cheers Oleg On Oct 15, 2015, at 1:03 PM, David Klim <[email protected]<mailto:[email protected]>> wrote: Thanks for the answers! So I guess I will need to create the flow programatically using Nifi REST API depending on the specifics of the cluster being setup, essentially: Create processor group -> instantiate template Will give that a try. Long term, I thing Nifi could accept several flows definitions in the config. Cheers ________________________________ From: [email protected]<mailto:[email protected]> Date: Thu, 15 Oct 2015 12:30:19 -0400 Subject: Re: Start flow automatically on Nifi start To: [email protected]<mailto:[email protected]> David, To expand on the second part of Andrew's answer, you can make templates of the Process Groups you divide your flow into so that you can add only the ones you need to any given cluster. Brandon On Thu, Oct 15, 2015 at 12:16 PM, Andrew Grande <[email protected]<mailto:[email protected]>> wrote: - I would like to start some of the flows whenever the nifi server is restarted. I think I can use 'nifi.flowcontroller.autoResumeState' to achieve that. Or would that start all processors? Yes, that's the purpose of this property and it's enabled by default. Did you try it and not see expected behavior? - I am creating a modular architecture, and depending on the modules that get deployed on a given cluster, I only need part of the flow. Is there a way to split the flow into several parts that can be independently added? I would go with Processing groups and configure input & output ports for each. Andrew
