[
https://issues.apache.org/jira/browse/NIFI-9993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17582780#comment-17582780
]
Peter Turcsanyi commented on NIFI-9993:
---------------------------------------
[~mayki] This issue was about waiting for archive clean-up while there are no
archive files actually (so nothing to clean up).
Based on the log in your previous comment, there are 2 archive files that can
be cleaned up and there should be similar logs a bit later:
{code:java}
INFO [Cleanup Archive for default] o.a.n.c.repository.FileSystemRepository
Successfully deleted 2 files (xx.xx MB) from archive
INFO [Cleanup Archive for default] o.a.n.c.repository.FileSystemRepository
Archive cleanup completed for container default; will now allow writing to this
container. Bytes used = xxx.xx GB, bytes free = xx.xx GB, capacity = xx.xx
GB{code}
Could you please check if you can see these logs?
So this can happen when the content repository size reaches a limit (more
precisely the disk partition where the content repo resides exceeds a disk
usage limit) and then it is not allowed to write more new FF content until the
archive files gets cleaned up (to make more space for the new files).
You can reduce the chance of this happening by setting the
{{nifi.content.repository.archive.backpressure.percentage}} property 10-20%
higher than {{nifi.content.repository.archive.max.usage.percentage}} in
{{{}nifi.properties{}}}.
More info in the [Admin
Guide|https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#file-system-content-repository-properties]:
{{nifi.content.repository.archive.*}} config properties.
cc [~malthe]
> Processors cannot write to Content Repo: Unable to write flowfile content to
> content repository container default due to archive file size constraints;
> waiting for archive cleanup
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-9993
> URL: https://issues.apache.org/jira/browse/NIFI-9993
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.17.0, 1.16.2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Sometimes, we can see NiFi log the following log message over and over:
> {code:java}
> 2022-05-05 10:47:03,267 WARN [Timer-Driven Process Thread-142]
> o.a.n.c.repository.FileSystemRepository Unable to write to container default
> due to archive file size constraints; waiting for archive cleanup {code}
> However, we can also see that there's nothing in the archive to cleanup,
> based on the fact that we also continually see this log message:
> {code:java}
> 2022-05-05 10:01:02,515 INFO [Cleanup Archive for default]
> o.a.n.c.repository.FileSystemRepository Successfully deleted 0 files (0
> bytes) from archive {code}
> If there are any files in the archive directory, we should see them getting
> cleaned up. The fact that we constantly see "Successfully deleted 0 files (0
> bytes) from archive" implies there is nothing in the archive.
> But if there is nothing in the archive, then we should not be seeing any
> notices about "Unable to write to container default due to archive file size
> constraints."
> This results in processors getting blocked for indefinite periods of time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
