Hi Team, Below are the basic steps that I am following to upgrade Nifi from version 1.23.2 to version 2.3.0 on my RHEL 9 server: unzip nifi newer version: unzip nifi-2.3.0-bin.zip copying flow files from older to newer version: cp nifi-1.23.2/conf/flow.* nifi-2.3.0/conf/ copying state directory from older to newer version: cp -r nifi-1.23.2/state nifi-2.3.0/state/ update nifi properties for sensitive prop key: nifi.sensitive.props.key=<<same as older version>> start nifi: sh nifi-2.3.0/bin/nifi.sh start Problem Statement: I am getting the Nifi UI console for newer verion (Nifi-2.3.0). All the processGroups Or Processors those were in older verion copied to new version as well. But few processors (like joltTransformation, publishKafka and etc), it still showing that those are using 1.23.2 nar file. Troubleshooting steps, but did not work: Though I have deleted the work directory and revalidated that lib is not using any nar file of older version. Delete work directory: rm -rf nifi-2.3.0/work/* Delete lib directory with 1.23.2 in case if it has: rm -rf nifi-2.3.0/lib/*.1.23.2*.nar restart nifi service: sh nifi-2.3.0/bin/nifi.sh restart I even manually changed the version in flow.json and flow.xml file from 1.23.2 to 2.3.0. Doing this the libbrary is 2.3.0 now, but in invalid state. Can you please mention the steps that I am missing here while upgrade from 1.23.2 to 2.3.0? Why not all the processoris getting upgraded as expected? ... View more

Hi Team, I am getting Authentication Error in ConsumeIMAP 1.23.2and ConsumePOP3 1.23.2 processor. Details are descrideb as below: Hostname : outlook.office365.com Port : 995( For POP3)/993 (For IMAP) Autherization Mode : OAUTH2 (Also Manually verified using the details of autherization serverURL and clientID/Secret, it has all relevant access to generate token) Error Details: ConsumePOP3[id=x3603x64-5f1c-1219-xxxx-xxxx34ffc1] Processing failed: org.apache.nifi.processor.exception.ProcessException: Failed to receive messages from Email server: [javax.mail.AuthenticationFailedException - Read timed out - Caused by: javax.mail.AuthenticationFailedException: Read timed out   ... View more

Hi Team, I want to achive the below mentioned transformation in Nifi. using any processor. Please help me to get this done. sample input: { "date": "35 days 11:13:10.88", "key1": "value1", "keyToBeMapped1": "hostname.com", "key2": "value2", "key3": "value3", "key4": "value4", "keyToBeMapped2": "High Paging Rate", "key5": "PAGING", "keyToBeMapped3": "A high paging activity has been detected on host abc.lab.com. This could mean that too many processes are being run", "Entity OID": "keyToBeMapped1", "Parameter": "keyToBeMapped2", "Description": "keyToBeMapped3" } Expected Output: { "date": "35 days 11:13:10.88", "key1": "value1", "keyToBeMapped1": "hostname.com", "key2": "value2", "key3": "value3", "key4": "value4", "keyToBeMapped2": "High Paging Rate", "key5": "PAGING", "keyToBeMapped3": "A high paging activity has been detected on host abc.lab.com. This could mean that too many processes are being run", "Entity OID": "hostname.com", "Parameter": "High Paging Rate", "Description": "A high paging activity has been detected on host abc.lab.com. This could mean that too many processes are being run" } Regards, Priyanka ... View more

Hi Team, I am using HandleHttpRequest to receive data in Nifi (version 1.23.2), and number of nodes in a Nifi cluster is 3. Now, there are possibilities of receiving data on load-balancer which is distributing load in round-robin way. My requirement is to count the total number of events in a min on the cluster. How to achieve that? My current flow: haldleHttpRequest --> MergeRecord (bin age is 1 min) --> calculateRecordStats (to get count) But my current flow is counting the number of events received by a node in a min not the total number of received data in a cluster in 1 min. Please suggest.   Regards, Priyanka Mondal ... View more

Hi, I have gone through multiple community support link, where it is mainly saying  to start cluster, say, 50MB/s And 1000 events/sec sustained throughput for average Flow is: 3 nodes each with: CPU: 8+ cores (16 is preferred) Memory: 8+ GB Disk: 6 disks, each 1TB disks (could be spinning or SSD) Referred link: https://community.cloudera.com/t5/Community-Articles/NiFi-Sizing-Guide-Deployment-Best-Practices/ta-p/246781 My Nifi (version 1.23.2) cluster maintaining below hardware configuration, where Disk is a concern in my environment. Only one disk and all the repository is using the same default Nifi configuration. What will be expected throughput in these case ? 3 nodes each with: CPU: 8+ cores (16 is preferred) Memory: 8+ GB Disk: 1 disk of 500GB (could be spinning or SSD)   5 nodes each with: CPU: 8+ cores (16 is preferred) Memory: 8+ GB Disk: 1 disk of 500GB (could be spinning or SSD)   7 nodes each with: CPU: 8+ cores (16 is preferred) Memory: 8+ GB Disk: 1 disk of 500GB (could be spinning or SSD) ... View more

Hi, I am using 3 node NiFi (Version: 1.23.2) cluster. If a node goes down, it is known that the flow can be directed to another node, but what about the data that is queued in the failed node? Is there anyway to replicate the data from failed node to other node? or will have to wait until the node comes back up? Please explain how to handle this scenario. ... View more