[
https://issues.apache.org/jira/browse/NIFI-9056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422249#comment-17422249
]
Andrew Heys commented on NIFI-9056:
-----------------------------------
[~markap14], thanks for all the information. I have had some difficulty running
the diagnostic command with the verbose as most of the time it errors with the
message: Exception in thread "main" java.net.SocketTimeoutException. My next
step is to setup the indexed provenance fields that you recommended, but
"contentClaimIdentifier" throws a invalid configuration error.
[~slyouts], yes we do have custom processors running. In my test cluster, I was
having trouble replicating the issue when I was just using the standard
processors. I setup another test flow using the same custom processors as my
production flow and I see the same behavior with the content repo disk filling
up. I need to do some more tests to provide something more conclusive to go on.
I saw some of [~markbean]'s debugging, and it is definitely possible that it is
originating from a .clone() session call.
> Content Repository Filling Up
> -----------------------------
>
> Key: NIFI-9056
> URL: https://issues.apache.org/jira/browse/NIFI-9056
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.13.2
> Reporter: Andrew Heys
> Priority: Major
>
> We have a clustered nifi setup that has recently been upgraded to 1.13.2 from
> 1.11.4. After upgrading, one of the issues we have run into is that the
> Content Repository will fill up to the
> nifi.content.repository.archive.backpressure.percentage mark and lock the
> processing & canvas. The only solution is to restart nifi at this point. We
> have the following properties set:
> nifi.content.repository.archive.backpressure.percentage=95%
> nifi.content.repository.archive.max.usage.percentage=25%
> nifi.content.repository.archive.max.retention.period=2 hours
> The max usage property seems to be completed ignored. Monitoring the nifi
> cluster disk % for content repository shows that it slowly fills up over time
> and never decreasing. If we pause the input to entire nifi flow and let all
> the processing clear out with 0 flowfiles remaining on the canvas for 15+
> minutes, the content repository disk usage does not decrease. Currently, our
> only solution is to restart nifi on a daily cron schedule. After restarting
> the nifi, it will clear out the 80+ GB of the content repository and usage
> falls down to 0%.
>
> There seems to be an issue removing the older content claims in 1.13.2.
> Thanks!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
