Mark beat me to the reply but it does appear our documentation is lacking. I've opened up an issue to include/improve this aspect in one of our upgrade and/or admin guides. https://issues.apache.org/jira/browse/NIFI-3665
Good question and thanks for reaching out. On Thu, Mar 30, 2017 at 7:31 PM, Mark Payne <[email protected]> wrote: > Hi Wes, > > Moving the state directory outside of the nifi home directory is > definitely a good idea. Otherwise processors would lose state so List* > processors, for instance, would start over from the beginning. > > Thanks > -Mark > > Sent from my iPhone > > > On Mar 30, 2017, at 7:07 PM, Wes Lawrence <[email protected]> wrote: > > > > I just wanted to confirm something, but I couldn't find anything online. > > > > A lot of docs that talk about setting NiFi up from a System Admin's > point-of-view, mention changing config to move several folders out of the > NiFi root dir. These typically include all 4 repositories, as well as files > like the flow.xml.gz. > > > > I see most guide leave the 'work' dir in place, so I assume when a new > version comes out, nothing is lost if 'work' is deleted. > > > > However, I'm not sure about the 'state' dir. Should this exist outside > of the root dir, if the idea is to replace NiFi's root dir with a new > version, or does it also get re-built like 'work'? Does it make a > difference when running single node vs (master-less) cluster? > > > > Thanks for any advice in advance, > > --Wes >
