[
https://issues.apache.org/jira/browse/NIFI-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383582#comment-16383582
]
ASF GitHub Bot commented on NIFI-4165:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2502
@alopresto This is not really for a corrupted flowfile repository but
rather for a flowfile repo that points to content that no longer exists. So the
easiest thing would be to create a GenerateFlowFile that generates at least 1
byte of data, then stop NiFi with data queued up and blow away the content
repo..... or change your nifi.properties to look at a different location for
the content repo.
> Update NiFi FlowFile Repository Toolkit to provide ability to remove
> FlowFiles whose content is missing
> -------------------------------------------------------------------------------------------------------
>
> Key: NIFI-4165
> URL: https://issues.apache.org/jira/browse/NIFI-4165
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Tools and Build
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
>
> The FlowFile Repo toolkit has the ability to address issues with flowfile
> repo corruption due to sudden power loss. Another problem that has been known
> to occur is if content goes missing from the content repository for whatever
> reason (say some process deletes some of the files) then the FlowFile Repo
> can contain a lot of FlowFiles whose content is missing. This causes a lot of
> problems with stack traces being dumped to logs and the flow taking a really
> long time to get back to normal. We should update the toolkit to provide a
> mechanism for pointing to a FlowFile Repo and Content Repo, then writing out
> a new FlowFile Repo that removes any FlowFile whose content is missing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
