Member since
01-16-2023
11
Posts
0
Kudos Received
0
Solutions
03-27-2023
09:57 PM
Hi @MattWho Thanks for the reply. I know that "Best Effort" and "Guarantee single node" delivery setting in the PublishKafka processor have nothing to do with the NiFi nodes in the NiFi cluster. This has to do with the nodes in the destination Kafka setup. My query is when i set the options as "Guarantee single node" and there are 3 kafka nodes. So when one of the kafka node is down, the publishkafka processor will try with other two kafka nodes, is my understanding right? Thanks
... View more
03-22-2023
11:51 PM
Hi, I have query on "Delivery guarantee" parameter in publishKafka processor in NIFI. I have query on below two option supported for the "Delivery guarantee" 1. Best effort 2. Guarantee single node delivery I know that the "best effort" does not wait for the ack/response from kafka, but in case of publish failure, when either of the above two option is set, will NIFI try to publish among the available nodes? Like in my setup its the cluster of three kafka nodes. If one of the node is down or if we observe connection timeout issue with one of the node, will NIFI tries to publish with other available nodes? Thanks
... View more
Labels:
- Labels:
-
Apache NiFi
03-22-2023
09:56 PM
Hi @MattWho I am not able to find those 3 flow files in provenance lineage, because the test was performed on March 20th and the oldest data i could find is from March 22nd in data provenance lineage. As per NIFI UI, the version is "Apache NIFI Version 1.9.0" , seems like we need to upgrade to 1.16 as the version is older(1.9.0)
... View more
03-22-2023
10:14 AM
Hi @MattWho I am not able to found those 3 flow files yet. Yes i am auto terminating the success relationship out of logAttribute processor, i will check regarding DROP events and let you know. And also let me check on the NIFI version we are using. Thanks for the reply
... View more
03-21-2023
11:13 PM
Hi @MattWho Thanks for the reply. The log message which are missing are the custom logs which we added using "logAttribute" processor in NIFI. we are using NIFI for kafka, when kafka publish is success or failure we log some message and this done using the logAttribute processor. These log messages are important to us to identify if all the messages are successfully published to kafka or not. we are observing that few of the custom logs added using logAttribute processor are missing. Please let me know the possible reason for these log messages missing. And please note that this issue is seen only during HA testing, like bringing down one NIFI instance and bringing it up back. Thanks.
... View more
03-20-2023
10:27 PM
Hi, I have two NIFI instance running and i am sending data. Both the nodes receives the data in random order. when i kill one of NIFI instances(first instance), all the data is processed by other NIFI instance(Second instance). And again when i bring back the other NIFI instance which was killed , the data is distributed among them in random order. Here there is no data loss observed, but we are observing some log messages are missing in the nifi-app.log as part of this restart. For example, during this testing if i have sent 100 messages, i see only log messages for 97 messages. Is this expected in NIFI or is there a way we can fix this issue? Is it related to gracefully shutting down the NIFI? Any help would be appreciated. Thanks
... View more
Labels:
- Labels:
-
Apache NiFi
03-15-2023
09:20 AM
Hi, I am using NIFI to consume and publish data using kafka. I have some queries on offset commit to ensure there is no data loss. Currently as per NIFI logs, the consumerconfig shows that "enable.auto.commit= false", this means that the offset are committed manually. Internal are these commits happening synchronously or asynchronously in NIFI? how to check this? And also in offset we have two types in kafka 1. current offset (Sent records)- This is used to avoid resending same records again to the same consumer 2. committed offset (processed records) - It is used to avoid resending same records to a new consumer in the event of partition rebalance. Regarding committed offset, This is kind of a indication sent back to kafka broker by consumer stating that the messages are consumed successfully? is my understanding right? Any help would be appreciated.
... View more
Labels:
- Labels:
-
Apache NiFi
03-14-2023
03:30 AM
Hi , Currently i am using NIFI to consume and publish data using kafka and i have a requirement to perform retry only for topicAuthorizationException thrown by NIFI processor (publishKafka processor). Like similar to RouteonAttribute, is there any processor or any log attribute through which i can parse or read this topicAuthorizationException error , so that i can perform retry? when kafka topic does not exist, NIFI throws below exception, the same is seen in nifi-app.log, i need to know how can we read this error in NIFI org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized to access topics: [test_topic]
... View more
Labels:
- Labels:
-
Apache NiFi
03-01-2023
11:19 PM
Hi, I am observing that kafka publish is failing in NIFI when i send one success and failure data alternatively. The scenario we are testing is, i am sending one success data and other one failure data. when i say failure data, i have removed the permission for the topic so that publish fails. for success data , topic is - svc_123 for failure data , topic is - svc_456 i removed publish permission for topic "svc_456" so that publish fails and goes to retry flow. i am sending data alternatively for topic "svc_123" and "svc_456". In this scenario, i see that even for topic "svc_123" the publish is failing. Not sure why the publish is failing for topic "svc_123" even though all permissions are given. And this scenario is seen when we send one success and one failure data as i have explained above. From NIFI logs no much info on why publish fails for "svc_123". To add on, when i send 3 messages for svc_123 followed by 3 messages for svc_456 , its working as expected, the issue is seen when data is sent alternatively Any help would be appreciated Thanks
... View more
Labels:
- Labels:
-
Apache NiFi
01-16-2023
11:17 PM
Currently i am observing that there is size limit on the maximum characters on "log prefix" property in logAttribute nifi processor. is there a way i can increase the log prefix size?
... View more
Labels:
- Labels:
-
Apache NiFi