Andrew Grande created NIFI-2001: ----------------------------------- Summary: Introduce a 'safe' startup mode Key: NIFI-2001 URL: https://issues.apache.org/jira/browse/NIFI-2001 Project: Apache NiFi Issue Type: Improvement Affects Versions: 0.6.1 Reporter: Andrew Grande
*Driver*: after NiFi crashes (e.g. with OOME), one needs to go in and manually flush queues or partially enable/disable flows to let them run and drain data. Also, if, for some reason, NiFi was sent into a CPU or I/O death spiral by the flow (e.g. a design mistake, or an unexpected spike in the data without backpressure controls configured). Today it's not possible without directly hacking the flow.xml.gz. This becomes even more troublesome in a clustered environment. *Proposal*: add a 'safe' switch/mode to NiFi, which will let it start up with full UI and infrastructure controls, but explicitly stopping all flows and CS. E.g. invoking *nifi.sh start -safe* on command line. Internally, the following should happen: * NiFi starts up as normal, with all libraries, plugins, etc. * However, *none* of the processorts, CS & groups are started/enabled -- This message was sent by Atlassian JIRA (v6.3.4#6332)