[
https://issues.apache.org/jira/browse/NIFI-9993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536811#comment-17536811
]
ASF subversion and git services commented on NIFI-9993:
-------------------------------------------------------
Commit b25201dd222d8847427bddd6c5a681d41b613bf2 in nifi's branch
refs/heads/NIFI-9428 from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b25201dd22 ]
NIFI-9993: Fixed bug in initialization in which the Content Repo did not
properly increment the counter for how many files exist in the archive
directories. This was causing the counter to become negative in some cases,
which caused processors to incorrectly pause, waiting for content archive
cleanup to occur when, in fact, there were no files archived
Signed-off-by: Joe Gresock <[email protected]>
This closes #6021.
> 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.7#820007)
