Skip to content

NIFI-6559 FlowFile Repo Journal Recovery Should not Fail if External …#3655

Closed
patricker wants to merge 1 commit intoapache:masterfrom
patricker:NIFI-6559
Closed

NIFI-6559 FlowFile Repo Journal Recovery Should not Fail if External …#3655
patricker wants to merge 1 commit intoapache:masterfrom
patricker:NIFI-6559

Conversation

@patricker
Copy link
Contributor

…Overflow Files are Missing

Description of PR

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.

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced
    in the commit message?

  • Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

  • Has your PR been rebased against the latest commit within the target branch (typically master)?

  • Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

  • Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
  • Have you written or updated unit tests to verify your changes?

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@patricker
Copy link
Contributor Author

After JIRA discussion, cancelling work.

@patricker patricker closed this Aug 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant