Member since
02-01-2019
70
Posts
5
Kudos Received
3
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
821 | 03-26-2024 07:53 AM | |
909 | 11-10-2022 10:58 AM | |
2230 | 09-08-2021 09:23 AM |
03-26-2024
07:53 AM
1 Kudo
Hi @bhagi This can happen when the processor is terminated but the thread is not finished. When NiFi terminates a processor it does an interrupt, once that happen it should do a graceful shutdown, but it's not guaranteed. In any case, that shouldn't stop the processor from running again. Please see the following question: https://community.cloudera.com/t5/Support-Questions/0-active-threads-1-terminated-QueryDatabaseTable-processor/m-p/234682 And the NiFi User guide: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#terminating_tasks Was your question answered? Make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.
... View more
11-10-2022
10:58 AM
1 Kudo
Every flowfile is held in memory for as long as the flowfile is in the flow, until it reaches a DROP event[1]. This means, that if you're writing a large attribute (such as a json) this will eventually add up to a large heap usage. Keep in mind that the attributes also get stored in data provenance so there's also an impact there. Biggest consequence to this a risk of NiFi going OOM, then failing to load the flowfile repository on startup. If the flowfile repo is too large it can also take longer for NiFi to start up, or also go OOM on startup while trying to load the repositories. This is also touched on the Anti-patterns video[2] [1]https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#provenance_events [2]https://www.youtube.com/watch?v=RjWstt7nRVY
... View more
06-14-2022
11:59 AM
Hi @yagoaparecidoti, Seems due to the configs NiFi is just using the identity instead of the complete DN. Without having more information you could try the following: 1. Change the initial admin identity to "user.bind" 2. Save and stop nifi 3. Remove the current users.xml and authorizations.xml from /var/lib/nifi 4. Start NiFi. It should recreate the users.xml and authorizations.xml files, please note that any customizations will be lost and will need to be recreated.
... View more
05-03-2022
11:58 AM
1 Kudo
Hello, You need to change this on Cloudera Manager > NiFi > Configs > Search for "logback_safety_valve" Paste the complete contents of the logback.xml in logback_safety_valve
... View more
04-14-2022
12:51 PM
KRB5CCNAME is an environment variable that Cloudera Manager sets, it'd change the filename for newly created kerberos tickets from the default "krbc5cc_<uid>" to krb5cc_cldr. https://web.mit.edu/kerberos/krb5-1.6/krb5-1.6/doc/klist.html If needed, you can unset it by adding the following to CM > NiFi > Configs > Filter for "nifi-env.sh" unset KRB5CCNAME
... View more
12-07-2021
05:07 PM
Hi @IAJ, typically this happens when the local flow is different from the cluster flow, this can be due to a mismatch in processors, connections, etc. Does this persist after the following steps? 1. Stop NiFi on this node 2. Copy the flow.xml.gz from the current coordinator to the failing node 3. Start NiFi
... View more
09-08-2021
09:23 AM
2 Kudos
Hi Joe, You could use ControlRate to set the max number of flowfiles per second/minute that needs to be routed. In order to periodically clean the incoming queue you can set a Flowfile Expiration on the incoming connection. Connection config: ControlRate config: With this, flowfiles on the connection will be cleared after they've been for more than 30 seconds on the queue.
... View more