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]

Cloudera Community

Support Questions

Find answers, ask questions, and share your expertise
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

Who agreed with this solution

avatar
author-rank MattWho author-rank
Master Mentor

Created ‎07-07-2020 05:31 AM

@venkii 

 

What version of NiFi are you running?

There are a set of bugs identified here that are likely related to the issue you described:
https://issues.apache.org/jira/browse/NIFI-5948
https://issues.apache.org/jira/browse/NIFI-6020
https://issues.apache.org/jira/browse/NIFI-6027

 

The good news is that these have all since been resolved.  
I would recommend upgrading your NiFi to a version 1.10 or newer.
Or HDF 3.4.1.1 or newer
Or CFM 1.0.1 or newer

 

As a workaround, you could shutdown you NiFi and search the users.xml and authorizations.xml file for uuid "938eb61e-bbc4-383a-8475-aee80541b5a5" and remove all references to it.  You would then need to make the exact same changes to the users.xml and authorizations.xml file on every other node in your NiFi cluster or copy the corrected files from one node to the other nodes.

 

Hope this helps,

Matt

View solution in original post

4,450
1
Who agreed with this solution