Member since
03-01-2018
6
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1041 | 06-14-2021 09:24 AM |
06-14-2021
09:25 AM
1 Kudo
I think I figured out with this issue on my side and I share my results with you. I deal with very small and very huge contents, the default values for properties hereafter are not appropriate (Claim size retained ...), so I decrease drastically the values as follows: nifi.content.claim.max.appendable.size=10 MB ==> 5MB nifi.content.claim.max.flow.files=100 ==> 50 nifi.content.repository.archive.max.retention.period=12 hours ==> 2 hours Until now, the platform doesn't freeze anymore. Jean-Louis
... View more
06-14-2021
09:24 AM
I think I figured out with this issue. I deal with very small and very huge contents, the default values for properties hereafter are not appropriate (Claim size retained ...), so I decrease drastically the values as follows: nifi.content.claim.max.appendable.size=10 MB ==> 5MB nifi.content.claim.max.flow.files=100 ==> 50 nifi.content.repository.archive.max.retention.period=12 hours ==> 2 hours Until now, the platform doesn't freeze anymore. Jean-Louis
... View more
05-20-2021
12:45 AM
Dear, I experienced the same situation but after a migrtion from 1.11.4 to 1.13.2. Have you solve your problem? Jean-Louis
... View more
05-18-2021
11:42 PM
Yes, check this url: Support (cloudera.com)
... View more
05-18-2021
07:47 AM
Dear all, After migrating an historical flow from 1.11.4 to 1.13.2, without any changes, after a while, the limits are raised but the content repository is never cleaned. I restart nifi, and the content-repository is cleaned. Thx for your help Jean-Louis OS : Ubuntu : 20.04.2 Java : OpenJDK Runtime Environment (build 1.8.0_292-8u292-b10-0ubuntu1~20.04-b10) Nifi properties: # Content Repository nifi.content.repository.implementation=org.apache.nifi.controller.repository.FileSystemRepository nifi.content.claim.max.appendable.size=10 MB nifi.content.claim.max.flow.files=100 nifi.content.repository.directory.default=/data3/nifi_repositories/content_repository nifi.content.repository.archive.max.retention.period=12 hours nifi.content.repository.archive.max.usage.percentage=50% nifi.content.repository.archive.enabled=true nifi.content.repository.always.sync=false nifi.content.viewer.url=/nifi-content-viewer/ nifi.content.repository.encryption.key.provider.implementation= .
... View more
Labels:
- Labels:
-
Apache NiFi
03-01-2018
08:16 PM
I had the same problem because I would like to reuse keystore created to securized Nifi UI and because of the usage dedicated to Nifi (TLS including client authentication), it can't be simply use to activate TLS. Symptom: java.net.BindException: Address already in use: bind Clue: If you search for the the first exception, in my case, it was "java.security.UnrecoverableKeyException: Cannot recover key" So I guess, the server can't get the key even if SSLContext starts correctly and, as the server starts anormally, Nifi tries to restart and then a Bind exception raises. I just regenerated a very classic jks store for server authentication usage using keytool -genkey ... and all went like a charm ... Hope that help Jean-Louis , I had the same problem because I would like to reuse keystore created to securized Nifi UI and because of the usage dedicated to Nifi (TLS including client authentication), it can't be simply use to activate TLS. Symptom: java.net.BindException: Address already in use: bind Clue: If you search for the the first exception, in my case, it was "java.security.UnrecoverableKeyException: Cannot recover key" So I guess, the server can't get the key even if SSLContext start correctly !! I just regenerated a very classic jks store for server authentication usage using keytool -genkey ... and all went like a charm ... Hope that help
... View more