Thanks, but what I cannot figure out is why du -h is reporting that the content repository is only a few GB and then suddenly tens of GB are released when NiFi shuts down. It's like the OS cannot accurately report who is claiming that much space.
On Wed, Dec 12, 2018 at 2:19 PM Michael Moser <[email protected]> wrote: > Hi Mike, > > I spent some time looking into this about a year ago. Here are some JIRA > tickets that describe what I think you are seeing. > > https://issues.apache.org/jira/browse/NIFI-3376 > https://issues.apache.org/jira/browse/NIFI-3736 > https://issues.apache.org/jira/browse/NIFI-4287 > > Regards > > > On Wed, Dec 12, 2018 at 1:07 PM Mike Thomsen <[email protected]> > wrote: > >> I configured the content repository to append 10 files per flowfile >> because I'm dealing with a lot of decompressing and recompressing of small >> files. The content repo goes up and down appropriately as the content >> claims are removed, but I noticed that after a lot of heavy processing >> sometimes 20-25GB (on a 100GB hdd) would stay used (as shown by df -h) >> until I stop NiFi. Then it suddenly gets purged. >> >> Weird part is that when I do du -h on the whole NiFi folder where things >> are stored, I don't see anywhere that much disk space being allocated. >> >> Anyone have any ideas on what might be going on? >> >> Thanks, >> >> Mike >> >
