Member since
07-18-2024
4
Posts
1
Kudos Received
0
Solutions
01-07-2025
12:29 PM
Dear Sirs, I have the following problem with my nifi cluster, it takes a long time to run a flow and when it does it presents the following error: Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to org.apache.nifi.processor.exception.TerminatedTaskException: org.apache.nifi.processor.exception.TerminatedTaskException Nifi version: 1.11.4 Zookeeper: external, apache-zookeeper-3.6.3 I performed the following actions seen in this previous post: https://community.cloudera.com/t5/Support-Questions/Apache-Nifi-ListSFTP-Processor-Failed-to-properly-initialize/m-p/366854 My state-managemnet. <cluster-provider> <id>zk-provider</id> <class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class> <property name="Connect String">node-1:2181,node-2:2181,node-3:2181</property> <property name="Root Node">/nifi</property> <property name="Session Timeout">10 seconds</property> <property name="Access Control">Open</property> </cluster-provider> and the zookeeper properties with the following: server.1=node-1:2888:3888;2181 server.2=node-2:2888:3888 ;2181 server.3=node-3:2888:3888;2181 Please I need support, I waste a lot of time testing and implementing flows because of this problem
... View more
Labels:
- Labels:
-
Apache NiFi
01-02-2025
01:59 PM
This solution is not concrete enough, I made the suggested changes for this error "Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to org.apache.nifi.processor.exception.TerminatedTaskException: org.apache.nifi.processor.exception.TerminatedTaskException", but I still have the problem, modify the state-management.xml, as follows, <cluster-provider> <id>zk-provider</id> <class>org.apache.nifi.controller.state.providers.zookeeper.ZooKeeperStateProvider</class> <property name="Connect String">node-1:2181,node-2:2181,node-3:2181</property> <property name="Root Node">/nifi</property> <property name="Session Timeout">10 seconds </property> <property name="Access Control">Open</property> and the zookeeper properties with the following: server.1=node-1:2888:3888;2181 server.2=node-2:2888:3888 ;2181 server.3=node-3:2888:3888;2181 I restarted zoo and nifi and the problem is not solved. What's more, I have a slow process to execute. When I execute the flow, the processors take a long time, more than 10 minutes to start. and does not run the generateflowfile processor. The processor previously when the cluster worked well the EvaluateJsonPath processor executed in milliseconds now it gets stuck and takes a long time to parse the json where there are some periods of data from to, so that the process works segmented with data, after the select the processors are configured as multitasking, I have nifi 1.11.4 and separately zookeeper 3.6.3
... View more
07-18-2024
10:32 PM
431 / 5,000 Resultados de traducción Traducción And what is done in this case: Nothing about how the content repository works will have any impact on NiFi UI performance. A full content repository will howvere impact the overall performance of your NiFi dataflows. Because when you change nifi.content.repository.archive.enabled to false, in a cluster of 3 nodes, for example, nifi only raises 2 nodes, always the first one that starts and the second, that remains visible in the cluster, but the third , is left running only as a 1-1 clusterer
... View more
07-18-2024
08:49 PM
1 Kudo
This solution does not work: Node 1: ok node 2 bootstrap.log; Error creating bean with name 'flowController': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalStateException: Unable to initialize Flow because NiFi was configured to start an Embedded Zookeeper server but failed to do so 2024-07-18 23:15:49,164 ERROR [NiFi logging handler] org.apache.nifi.StdErr Shutting down... nifi_app_log; Error creating bean with name 'flowController': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalStateException: Unable to initialize Flow because NiFi was configured to start an Embedded Zookeeper server but failed to do so In node 3 dice nifi_app_log dice ERROR [node-2/xxx.xx.x.x:3888] o.a.z.server.quorum.QuorumCnxManager As I'm leaving the listener thread after 3 errors. I won't be able to participate in leader election any longer: xxx.xx.x.x:3888. Use zookeeper.electionPortBindRetry property to increase retry count bootstrap.log; no error We went from version 1.11.4 to 1.16.3 I lift the cluster solo once, then restart it and I don't lift it but
... View more