Hi @Koffi  Not sure if you have ambari metrics enabled?   If you dont then I would just simply delete the flow.xml.gz typically found under: on <node01>   /usr/hdf/current/nifi/conf   Assuming you have HDF managed by HDP ambari. And then restart your nifi   If you do have amabri metrics enabled then do the same thing but instead restart the nifi from the command line on node01 $NIFI_HOME/bin/nifi.sh restart <Assuming you set a runas user on your bootstrap.conf>  or run same command as user who will run nifi.   The reason ambari metrics plays a role here is that if you restart nifi from ambari AND you have ambari metrics enabled then once you remove the flow.xml.gz, ambari will see its missing and create a vanilla one with ambari metrics and will get a flow mismatch again.   Hope that helps!   Juan C. ... View more

@asmarz  The error is below in bold I   /usr/bin/hdp-select set oozie-client 3.1.4.0-315' returned 1. symlink target /usr/hdp/current/oozie-client for oozie already exists and it is not a symlink.   Possible cause the symlink is broken or exists and is pointing to different location or version  so removing symlink and reinstalling the client should resolve the issue Validate   Can you validate that the link exists?   Move the symlink mv /usr/hdp/current/oozie-client /usr/hdp/current/oozie-client_back   Recreate the symlink ln -s  /usr/hdp/3.1.0.0-78/oozie /usr/hdp/current/oozie-client   My version above is 2.1.0.0.x this should match your exact version   ... View more