[
https://issues.apache.org/jira/browse/NIFI-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne resolved NIFI-8728.
------------------------------
Resolution: Not A Problem
[~wildq] this is by design. The archiveCount here is not really relevant. When
the disk that the content repo is on reaches the configured threshold (50%),
the content repo will exert backpressure, preventing processors from writing to
it, until archival has run. This is done because on my operating systems
(including linux) creating and writing to a file can be more efficient/faster
than deleting the file. As a result, we can end up in a situation in which we
create data faster than we can delete it, which causes the content repo to fill
up all disk space. This forces the processors to stop and give the repo a
chance to cleanup.
It is not a perfect solution, but it it's working as designed. You can
certainly increase the threshold to something much higher than 50% if necessary.
> archiveCount below zero, all processors with content modified will blocked in
> "waiting for archive cleanup"
> ------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-8728
> URL: https://issues.apache.org/jira/browse/NIFI-8728
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Affects Versions: 1.12.0, 1.13.0, 1.12.1, 1.13.1, 1.13.2
> Environment: linux
> Reporter: wangliqiang
> Priority: Major
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> When I found the issue “claimantCount will never decrement to zero”，I restart
> the nifi instance and a new issue happened；
> Here is the log：
> 2021-06-23 10:33:02,788 INFO [main] o.a.n.c.repository.FileSystemRepository
> Found unknown file
> /data/nifi/nifi-1.13.2/content_repository/1/1624415033830-1 (286096 bytes) in
> File System Repository; archiving file
> 2021-06-23 10:33:57,786 DEBUG [Cleanup Archive for default]
> o.a.n.c.repository.FileSystemRepository Deleted archived ContentClaim with ID
> 1624415033830-1 from Container default because the archival size was
> exceeding the max configured size, {color:#FF0000}archiveCount -1{color}
>
> If i config "nifi.content.repository.archive.max.usage.percentage=50%",When
> the archiveCount is “-1” and disk storage is over 50% , all processors with
> content modified will blocked in the method "isWaitRequired()" !
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
