[
https://issues.apache.org/jira/browse/NIFI-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16909158#comment-16909158
]
Peter Wicks commented on NIFI-6559:
-----------------------------------
[~markap14] I don't disagree with any of the downsides/issues you outlined. Do
you have an idea for an option to work with this though? Because right now the
only option for fixing a corrupt journal is dropping the entire journal with
all changes.
> FlowFile Repo Journal Recovery Should not Fail if External Overflow Files are
> Missing
> -------------------------------------------------------------------------------------
>
> Key: NIFI-6559
> URL: https://issues.apache.org/jira/browse/NIFI-6559
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Peter Wicks
> Assignee: Peter Wicks
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When NiFi is journaling the FlowFile repository changes to disk it sometimes
> writes Overflow files if it exceeds a certain memory threshold.
> These files are tracked inside of the *.journal files as External File
> References. If one of these external file references is deleted or lost the
> entire journal fails to recover.
> Instead, I feel this should work more like FlowFile's that lose their queue,
> or Content in the Content Repository that has lost it's FlowFile. Log it,
> and move on.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
