You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2017/03/30 23:38:42 UTC
[jira] [Created] (NIFI-3665) Documentation doesn't cover handling
of local state directory in upgrade scenarios
Aldrin Piri created NIFI-3665:
---------------------------------
Summary: Documentation doesn't cover handling of local state directory in upgrade scenarios
Key: NIFI-3665
URL: https://issues.apache.org/jira/browse/NIFI-3665
Project: Apache NiFi
Issue Type: Improvement
Components: Documentation & Website
Reporter: Aldrin Piri
Priority: Minor
We had a user that was running a standalone instance of NiFi and was unsure of what to do with the state directory.
{quote}
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
{quote}
We don't seem to capture the idea of externalizing this to make upgrades easier in our Administrator's guide (https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#state_providers) nor in the Upgrade guide in our Wiki (https://cwiki.apache.org/confluence/display/NIFI/Upgrading+NiFi)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)