About DavidR

VikneshSK · ‎08-11-2020

I did this in root user, found the file and changed it there. But, how to change it for each node?

MattWho · ‎03-24-2020

@Koffi When a NiFi node attempts to connect to an existing NiFi cluster, there are three files that are checked to make sure they match exactly between the connecting node and the existing copies in the cluster. Those files are: 1. flow.xml.gz 2. users.xml (will only exist if NiFi is secured over https) 3. authorizations.xml (not to be confused with the NiFi authorizers.xml file. Will only exist if NiFi is secured over https) The output in the nifi-app.log of the node should explain exactly what the mismatch was the first time it tried to connect to the cluster. Hope this helps, Matt

DavidR · ‎02-27-2020

This is very good information. Where can I look for more documentation like this regarding specifically the modes other then "embedded"? Thank you in advance, David

DavidR · ‎02-18-2020

@MattWho Thank you once again for the information posted here. It solved our problem. I was able to run the flow in another cluster using nifi.sh instead of running it with ambari (and the encrypt tool it uses). copying nifi.sensitive.props.key in /etc/nifi/conf/nifi.properties from source cluster did the trick. BR, David

DavidR · ‎02-10-2020

I would also like to know this. Is Hive on Spark currently supported by HortonWorks? Since which version? Thanks in advance, David Resende

DavidR · ‎10-29-2019

@MattWho Thank you for your input. It works and It was invaluable.

Online	Offline
Last Visited	‎03-23-2020 02:10 PM

Member Since	‎10-07-2019 05:02 AM
Last Visited	‎03-23-2020 02:10 PM
Posts	13
Kudos received	4

Cloudera Community

Re: How to get rid of stale alerts in Ambari

Re: Can't connect to the nifi UI

Re: Introduction to Application Timeline Server

Re: NiFi Toolkit: Can't start NiFi with a ~75MB gz...

Re: Hive on Spark

Re: NIFI: How to turn on GC logging for NiFi?