If the schedule state was properly maintained across a restart, would the rolling-restart-to-update be fine?
On Thu, Mar 26, 2015 at 10:35 AM, Ricky Saltzer <[email protected]> wrote: > Hi - > > I have a 3 node NiFi cluster, and periodically I need to update the custom > NAR we use for our internal projects. Currently I'm just copying the new > NAR into the lib directory on each of the nodes (including the master), and > then restarting each daemon (bin/nifi.sh restart) individually. > > I'm curious if there's a better method than the one I'm using. The biggest > downside I'm seeing is that all my processors that I have scheduled to > execute once per day are being kicked off again, which is not the behavior > I want. I don't have these set to use a CRON based schedule, because there > is currently no way of having a CRON scheduled processor run on a single > node. > > -- > Ricky Saltzer > http://www.cloudera.com > -- Sean
