Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

disk io operations going up with volatile repositories

avatar
Expert Contributor

I have set following:

  1. nifi.flowfile.repository.implementation: org.apache.nifi.controller.repository.VolatileFlowFileRepository
  2. nifi.provenance.repository.implementation: org.apache.nifi.provenance.VolatileProvenanceRepository

With this, I expect disk io operations to go down(checked with nmon). But its just opposite and disk writes have gone up multiple times.

Why so?

1 ACCEPTED SOLUTION

avatar
Super Mentor

@manishg 

Same about of flowFiles per second processing after switching to the Volatile repositories?
Perhaps having FlowFile and provenance repositories in memory allows for faster processing of FlowFIles resulting in more read and writes to the content_repository which contains the actual content of each FlowFile.

If your NiFi should crash or restart you will lose everything in your volatile repositories.  The FlowFile repository holds all the FlowFile metadata for the FlowFiles currently being processed through your dataflows.   This means data loss in such events.

If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

View solution in original post

1 REPLY 1

avatar
Super Mentor

@manishg 

Same about of flowFiles per second processing after switching to the Volatile repositories?
Perhaps having FlowFile and provenance repositories in memory allows for faster processing of FlowFIles resulting in more read and writes to the content_repository which contains the actual content of each FlowFile.

If your NiFi should crash or restart you will lose everything in your volatile repositories.  The FlowFile repository holds all the FlowFile metadata for the FlowFiles currently being processed through your dataflows.   This means data loss in such events.

If you found any of the suggestions/solutions provided helped you with your issue, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt