Details
-
Task
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
1.13.2
-
None
Description
Our team recently upgraded to 1.13.2 from 1.11.4. The performance improvements caused a number of servers which see quite a bit of data to perform better. However, we began experiencing "frozen NiFi's". NiFi's that appear fine, but will not process any data. We determined the file I/O improvements from the 1.11.4 to 1.13.2 release were significant enough for us, that we increased the amount of data passing through them to go from the 50% archive to exceeding the 52% archive backpressure percentage prior to the archive job completing.
This locked-up all our NiFi's causing us to revert.
How did we figure this out?
We came across a mailing list email outlining the undocumented NiFi Property nifi.content.repository.archive.backpressure.percentage causing the issue.
This is a repeatable issue. Something more should be done to warn the user on the UI that this has happened. Until then. Here is a ticket outlining all of the missing properties in the Sys Admin Guide as compared to the real properties defined in NiFiProperties.java.
Default | |
Missing Core Properties | |
RESTORE_DIRECTORY = "nifi.restore.directory"; | ?? |
Missing Content Repository Properties | |
MAX_FLOWFILES_PER_CLAIM = "nifi.content.claim.max.flow.files"; | 100 |
CONTENT_ARCHIVE_BACK_PRESSURE_PERCENTAGE = "nifi.content.repository.archive.backpressure.percentage"; | 2% |
CONTENT_ARCHIVE_CLEANUP_FREQUENCY = "nifi.content.repository.archive.cleanup.frequency"; | 1 Second |
Missing Provenance Properties | |
PROVENANCE_ROLLOVER_EVENT_COUNT = "nifi.provenance.repository.rollover.events"; | Integer.MAX_VALUE |
PROVENANCE_REPO_DEBUG_FREQUENCY = "nifi.provenance.repository.debug.frequency"; | 1_000_000 |
Missing Web Properties | |
WEB_MAX_ACCESS_TOKEN_REQUESTS_PER_SECOND = "nifi.web.max.access.token.requests.per.second"; | 25 |
WEB_SHOULD_SEND_SERVER_VERSION = "nifi.web.should.send.server.version"; | TRUE |
Attachments
Issue Links
- links to