nifi.content.viewer.url=../nifi-content-viewer/
Regards,
Dnyaneshwar Pawar
From: Boris Tyukin
Sent: Wednesday, June 19, 2019 11:40 PM
To: users@nifi.apache.org
Subject: Re: Content repository data filling up disk...
we had the exact same issue and after the upgrade to 1.9.2 all is good
On Wed, Jun 19, 2019 at 1
we had the exact same issue and after the upgrade to 1.9.2 all is good
On Wed, Jun 19, 2019 at 1:28 PM Erik Anderson wrote:
> > Mark Payne
> > Version 1.9.1 introduced a bug [1] that resulted We ran into the same
> issues with NiFi filling up the disk with NiFi 1.9.1
> > 1.9.2 doesnt have the
> Mark Payne
> Version 1.9.1 introduced a bug [1] that resulted We ran into the same issues
> with NiFi filling up the disk with NiFi 1.9.1
> 1.9.2 doesnt have the problem. in the content repository not being properly
> cleaned up, which could cause you to run
> out of disk space.
I can confirm
0.7.4. I just got here a few weeks ago and have plans to move everything
up to 1.9.2, which I'm running myself. I'm probably a little premature
asking about what to look for here. I'll try to ask more direct
questions next. Thanks.
On 6/19/19 9:17 AM, Mark Payne wrote:
Russell,
I would also
Russell,
I would also be curious what version of NiFi you are running. Version 1.9.1
introduced a bug [1] that resulted
in the content repository not being properly cleaned up, which could cause you
to run out of disk space.
Thanks
-Mark
[1] https://issues.apache.org/jira/browse/NIFI-6150
On
Joe,
I am at the beginning of this, I admit. It's useful to understand the
bit about combining content. Our application is for ETL of medical
documents, contains myriad and complex interactions between points, the
documents leave NiFi at points, then return at others before finally
being entr
Russell
If data remains in the content repository beyond the specified archive
values then it suggests there is content remaining in the flow that is not
yet eligible to be removed/deleted. This is not always a direct "500 MB of
content waiting for delivery results in 500 MB of content in the con
Just in general, when this data begins to collect without clearing
itself out, what direction might I be looking for the cause? Ordinarily,
in our application, content doesn't collect flooding the disk and
threaten to bring the server down.
Thanks for any comments.
