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]

Support Questions

Find answers, ask questions, and share your expertise
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!

Minifi and Log Size

avatar
Expert Contributor

Hi Team ,

We are currently in Operations space with Minifi installed on remote server and successfully transmitting data to the Nifi server overlooked by a C2 server. One question that bothers us is that if Nifi went down or Minifi isnt able to connect to Nifi due to some reason or the other , would the Minifi logs grow huge as it is unable to transmit the data ???

Any information / best practices on this will be greatly appreciated

@Matt Burgess

@Matt Clarke

1 ACCEPTED SOLUTION

avatar
Expert Contributor

Ok , we managed to get the answer to this. If Minifi for some reason isnt able to transmit data to the Nifi server , the minifi content repository starts getting filled up and this needs to be avoided. So , we need to add some space to the filesystem that points to the content repository as a best practice in production.

View solution in original post

1 REPLY 1

avatar
Expert Contributor

Ok , we managed to get the answer to this. If Minifi for some reason isnt able to transmit data to the Nifi server , the minifi content repository starts getting filled up and this needs to be avoided. So , we need to add some space to the filesystem that points to the content repository as a best practice in production.