Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Strange behavior of nifi 1.5.0

Highlighted

Strange behavior of nifi 1.5.0

Explorer

Hello. Yesterday I noticed the mechanism of purging old files in content repository had not worked off. It was configured 12 hours, 20% of disk space, but it took about 80% of content repository, and files were of 14 days old. Any ideas why could this happen? Btw after restart of nifi purging the content repo worked and everything was ok. Who have faced such a problem?

3 REPLIES 3
Highlighted

Re: Strange behavior of nifi 1.5.0

Master Collaborator

@Henry Peterson What you are describing is normal behavior for the repository. You can find a much deeper dive into the details in the following article:

https://community.hortonworks.com/content/kbentry/82308/understanding-how-nifis-content-repository-a...

If this answer is helpful, please choose Accept

 


 


If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post.  


 


Thanks,



Steven

Re: Strange behavior of nifi 1.5.0

Explorer

I read this article twice but have no idea by what cause it could happen. Will you be kindly to explain? Btw I'm dealing with files of 100 MB which are splited into many small files.

Highlighted

Re: Strange behavior of nifi 1.5.0

New Contributor

Read the section on content archiving. If you have flow files in a content repo they are stored in a content claim (file). Claims can store more than 1 flowfile. Claims don't get unallocated or archived until all the flowfiles in the claim have cleared Nifi. Check for flow files in dataflow deadends and in connections handling errors.

From the article:

A content claim cannot be moved into the content repository archive until none of the pieces of content in that claim are tied to a FlowFile that is active anywhere within any dataflow on the NiFi canvas. What this means is that the reported cumulative size of all the FlowFiles in your dataflows will likely never match the actual disk usage in your content repository.

Don't have an account?
Coming from Hortonworks? Activate your account here