[NIFI-9993] 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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.17.0, 1.16.2
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 05/May/22 20:14
• Updated: 22/Aug/22 07:40
• Resolved: 09/May/22 16:22

Description

Sometimes, we can see NiFi log the following log message over and over:

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 

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:

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 

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.

Issue Links

• relates to: NIFI-10023 FileSystemRepository improperly tracks file archival count
• links to: GitHub Pull Request #6021