Thanks Michael, I could try turning off the content repository archive
feature. One thing I'm curious though is when I watched the content
repository folder when my nifi flow is still actively running, it kept
writing new empty files to the archive folder and some of them are old
flowfiles'
Maximum number of inodes is defined when you build a file system on a
device. You would have to backup your data, rebuild your file system and
tell it to allocate more inodes than the default (an mkfs option, I
think?), then restore your data.
You can turn off the NiFi content_repository
One Strange thing one of our testers found was that we're using the default
12hours archive and 50% disk space configuration, he noticed that when nifi
removed the archived files inside the content_repository, he checked the
inodes ' count didn't go down, then he tried to remove some of the
Hi Michael, the no space left on device occurred again and I checked the
inodes at the time and found it was indeed full, why would the inodes
become full and are there any solutions to get around this problem? Thanks.
/Ben
2017-12-13 13:36 GMT+08:00 尹文才 :
> Hi Michael, I
Hi Michael, I checked the system available inodes by running df -i command
and there're quite enough inodes in the system. I then removed all the
files in all repository folders and restarted
the system, I couldn't see the error again. I will continue to track the
problem to see what's causing it,
Greetings Ben,
The "No space left on device" error can also be caused by running out of
inodes on your device. You can check this with "df -i".
-- Mike
On Tue, Dec 12, 2017 at 1:36 AM, 尹文才 wrote:
> sorry that I forgot to mention the environment that caused this problem,
sorry that I forgot to mention the environment that caused this problem,
I'm using the latest nifi 1.4.0 release and installed it on centos 7.
2017-12-12 14:35 GMT+08:00 尹文才 :
> Hi guys, I'm running into a very weird problem, I wrote a processor
> specifically to extract
Hi guys, I'm running into a very weird problem, I wrote a processor
specifically to extract some data
and I found starting from yesterday it kept showing errors in the log, as
below:
2017-12-12 14:01:04,661 INFO [pool-10-thread-1]
o.a.n.c.r.WriteAheadFlowFileRepository Initiating checkpoint of