Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 07-21-2016 01:34 PM
I am aware that the NiFi bootstrap process can be configured to provide notifications in the event of a NiFi failure but I am wondering if we can configure the bootstrap process to not only detect and notify users of a failure but to also attempt to bring the NiFi process back to life? Am I missing an obvious config parameter in the guide?
Created 07-21-2016 06:43 PM
The boostrap process restarts NiFi when the main NiFi process dies. An easy test is to start a new NiFi and then kill -9 the main process and you'll immediately see it come back with a new pid.
OOM would probably be tricky because a lot of times the Java process does not die when encountering an OOM and sticks around in some bad state.
Created 07-21-2016 01:41 PM
@Brandon Wilson I believe the best way to do this would be to install NiFi on your system using
$NIFI_HOME/bin/nifi.sh install
and then using an OS level processing management tool (supervisord on Ubuntu for example) to monitor that process and then restart it based on configurations that you provide to the process management tool.
Created 07-21-2016 06:43 PM
The boostrap process restarts NiFi when the main NiFi process dies. An easy test is to start a new NiFi and then kill -9 the main process and you'll immediately see it come back with a new pid.
OOM would probably be tricky because a lot of times the Java process does not die when encountering an OOM and sticks around in some bad state.