About chitrarthasur

chitrarthasur · ‎08-05-2022

NiFi 1.16.3 Processor groups are not getting deleted. We are using open source NiFi 1.16.3 When we try to delete it showing connection with id **** is running. As we can see the processors using this connection are stopped and disabled even, but the connection shows running. However when we try to manually delete the connection it works. Any help is much appreciated. Thanks!

chitrarthasur · ‎03-29-2022

@araujo This is whats happening. So telnet is working fine but the curl is not working. The request does not hit the listener. However, after nifi restart it works, i.e it hits the listener. So path rules are also correct.

chitrarthasur · ‎03-08-2022

NiFi listener processor not responding though UI is up. The CPU, threads, Memory all are getting used almost nothing. No OOM also Can someone please give some pointers what can be done so the http listener processor keeps running

chitrarthasur · ‎01-19-2022

@DigitalPlumber The state file in local were deleted and the cluster is showing all the 3 nodes, thanks for the help. However, we are trying fault tolerance feature of NiFi, and when primary node goes down can see this message in other nodes: Cannot replicate request to Node nifi-hatest-03:9091 because the node is not connected Below is article which had same errors, but we cannot clean state file always as if one node goes down our NiFi cluster should be still available without manual intervention? https://community.cloudera.com/t5/Support-Questions/NiFi-Cannot-replicate-request-to-Node-nifi-domain-net-8443/td-p/283664

chitrarthasur · ‎01-19-2022

@DigitalPlumber We have removed all these files from all the 3 nodes, as we don't have any flows. sudo rm -f /hadoop/nifi/conf/flow.xml.gz sudo rm -f /hadoop/nifi/conf/users.xml sudo rm -f /hadoop/nifi/conf/authorizations.xml sudo rm -f /etc/nifi/3.5.2.0-99/0/state-management.xml sudo rm -f /etc/nifi/3.5.2.0-99/0/authorizers.xml And since its external zk, we are giving new root node to start with. But the issue still persists. The new root node is "nifi3" and here is what i see in zk, is it expected output? [zk: nifi-hatest-03:2181(CONNECTED) 2] ls /nifi3/leaders [Primary Node, Cluster Coordinator] [zk: nifi-hatest-03:2181(CONNECTED) 3] ls /nifi3/leaders/Primary Node Node does not exist: /nifi3/leaders/Primary [zk: nifi-hatest-03:2181(CONNECTED) 4] ls /nifi3/leaders/Cluster Coordinator Node does not exist: /nifi3/leaders/Cluster [zk: nifi-hatest-03:2181(CONNECTED) 5] ls /nifi3/components We have also verified these 2 props and it matches the respective hostnames: nifi.cluster.node.address= nifi.web.https.host=

chitrarthasur · ‎01-19-2022

Hello Guys, We have 3 node NiFi cluster and the NiFi version is 1.12.1 nifi-hatest-01 nifi-hatest-02 nifi-hatest-03 All the 3 nodes are in cluster, but not in UI. In all the 3 NiFi nodes, we see this 2 nodes in cluster mode: Now, as we see nifi-hatest-02 is the primary and cooridantor. And nifi-hatest-03 is not being shown here. In nifi-hatest-01, we see nifi-hatest-01 is connecting to nifi-hatest-02 2022-01-19 16:02:09,840 INFO [Clustering Tasks Thread-1] o.a.n.c.c.ClusterProtocolHeartbeater Heartbeat created at 2022-01-19 16:02:09,820 and sent to nifi-hatest-02:9088 at 2022-01-19 16:02:09,840; send took 20 millis In nifi-hatest-03, we see nifi-hatest-03 is also connecting to nifi-hatest-02 2022-01-19 16:02:09,840 INFO [Clustering Tasks Thread-1] o.a.n.c.c.ClusterProtocolHeartbeater Heartbeat created at 2022-01-19 16:02:09,820 and sent to nifi-hatest-02:9088 at 2022-01-19 16:02:09,840; send took 20 millis In nifi-hatest-02, we see nifi-hatest-02 is also connecting to all the 3 nodes as its coordinator: 2022-01-19 16:04:52,573 INFO [Process Cluster Protocol Request-30] o.a.n.c.p.impl.SocketProtocolListener Finished processing request 35f2ed1a-ca6f-4cc6-ab4a-6c0774fc9c6d (type=HEARTBEAT, length=2837 bytes) from nifi-hatest-03:9091 in 19 millis 2022-01-19 16:04:52,782 INFO [Process Cluster Protocol Request-31] o.a.n.c.p.impl.SocketProtocolListener Finished processing request 73d477cd-a936-4541-a854-03712cbc5fe9 (type=HEARTBEAT, length=2836 bytes) from nifi-hatest-02:9091 in 18 millis 2022-01-19 16:04:52,782 INFO [Clustering Tasks Thread-3] o.a.n.c.c.ClusterProtocolHeartbeater Heartbeat created at 2022-01-19 16:04:52,762 and sent to nifi-hatest-02:9088 at 2022-01-19 16:04:52,782; send took 19 millis 2022-01-19 16:04:53,916 INFO [Process Cluster Protocol Request-32] o.a.n.c.p.impl.SocketProtocolListener Finished processing request 4fbc39d9-5154-4841-b3be-ddde58b22cd2 (type=HEARTBEAT, length=2836 bytes) from nifi-hatest-01:9091 in 19 millis No errors regarding cluster in either of nodes. But still see 2 nodes only in UI. Also Cluster is using zk as cluster state provider. Another thing is that when we create a processor in any of the NiFi UI, it gets propagated to other nodes too! So functionality its kind of working.

Online	Offline
Last Visited	‎08-05-2022 12:08 AM

Member Since	‎01-19-2022 07:57 AM
Last Visited	‎08-05-2022 12:08 AM
Posts	6

Cloudera Community

NiFi 1.16.3 Processor groups are not getting delet...

Re: NiFi listener processor not responding though ...

NiFi listener processor not responding though UI i...

Re: NiFi Node showing 2 nodes and not respecting n...

Re: NiFi Node showing 2 nodes and not respecting n...

NiFi Node showing 2 nodes and not respecting node ...