Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NIFI-3039 Provenance Repository - Fix PurgeOldEvent and Rollover Size Limits (0.x) #1241

Closed
wants to merge 1 commit into from

Conversation

jskora
Copy link
Contributor

@jskora jskora commented Nov 17, 2016

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

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

  • [x ] 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.

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

  • [x ] Is your initial contribution a single, squashed commit?

For code changes:

  • [x ] 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?
  • If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
  • If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
  • If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
  • If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

  • Have you ensured that format looks appropriate for the output in which it is rendered?

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.

NIFI-3039 Provenance Repository - Fix PurgeOldEvent and Rollover Size Limits

Added low water mark for purgeOldEvents() to prevent thrashing on event cleanup.
Adjusted rollover high water mark to match purgeOldEvents() to prevent overrunning "nifi.provenance.repository.max.storage.size".
Moved high/low water marks to constants.
Adjusted looping logic in mergeJournals() to use ".firstKey()" instead of ".entrySet().iterator().next()" to avoid unnecessary object creation.

… Limits

* Added low water mark for purgeOldEvents() to prevent thrashing on event cleanup.
* Adjusted rollover high water mark to match purgeOldEvents() to prevent overrunning "nifi.provenance.repository.max.storage.size".
* Moved high/low water marks to constants.
* Adjusted looping logic in mergeJournals() to use ".firstKey()" instead of ".entrySet().iterator().next()" to avoid unnecessary object creation.
@joewitt
Copy link
Contributor

joewitt commented Jan 3, 2018

@jskora This is our oldest untouched PR. Do you still think it is good to go?

@markap14 Can you take a look?

@jskora
Copy link
Contributor Author

jskora commented Jan 3, 2018

@joewitt Since 0.x is end-of-life, this is OBE and should be closed.

IIRC, the root problem was writing records first and then checking afterward to see if storage limits were exceeded and a rollover needed. If the storage limits don't leave a margin before reaching the physical capacity, writes can fill the disk and crash the NiFi and possible the system. I looked at the 1.x repositories in depth since they were re-written, but if the same write-then-check behavior exists this could still be a problem.

@mosermw
Copy link
Member

mosermw commented Feb 8, 2018

@jskora I think you are the only one who can close this PR. Would you mind? Thanks!

@jskora
Copy link
Contributor Author

jskora commented Feb 8, 2018

Overcome by events.

@jskora jskora closed this Feb 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants