Member since
07-30-2019
944
Posts
197
Kudos Received
91
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1507 | 10-05-2021 01:53 PM | |
| 16331 | 09-23-2019 06:03 AM | |
| 6823 | 05-04-2019 08:42 PM | |
| 1502 | 06-11-2018 12:45 PM | |
| 12628 | 06-04-2018 01:11 PM |
06-29-2017
04:37 PM
What do the zookeeper logs show for the node that is having issues? Does it show the node trying to connect to zookeeper?
... View more
06-29-2017
12:05 PM
@shivanand khobanna
The ExecuteStreamCommand processor should be able to do what you need to do. You can access the attributes using the expression language. For instance if you have an attribute named jython1, using ${jython1} will return the value of that attribute and you can use as a parameter when calling your script.
... View more
06-28-2017
11:49 PM
1 Kudo
@Adda Fuentes
It looks like you are seeing this issue: Background retry falls into infinite loop of reconnection after connection loss Are all of the zookeeper instances running? Are you seeing any messages in the zookeeper logs?
... View more
06-27-2017
05:18 PM
@Akash S The optimum value for Maximum Timer Driven Thread count will be based on the number of CPU's your system has. Roughly we recommend between 2 and 4 times the number of CPU. So, if your system has 8 CPUs, assuming it isn't bear metal, then your max timer driven threads can be between 16 and 32. If you have a bare metal system, then you will have more room because of hyper-threading, so the values could be between 32 and 64. The Event Driven thread value can stay at 5, NiFi will not need more than that, no matter how many processors there are on the graph.
... View more
06-26-2017
01:21 PM
@Julio Cedeno First, if you want to use START_TLS authentication strategy, then your LDAP URL should look like ldaps://direccion:636. If you use SIMPLE, then the URL you have will work. How were the keystore and truststore generated? Have you configured NiFi to use the ldap-provider you configured in the login-idenitity-providers.xml file?
... View more
06-23-2017
12:59 PM
1 Kudo
@Jody H Here is a link to another question about the ListFile processor. I think you might be seeing the same behavior.
ListFile processor
... View more
06-22-2017
03:22 PM
1 Kudo
@mayki wogno To get your node back into the cluster. Copy the users.xml, authorizations.xml and the flow.xml.gz from one of the nodes in the cluster and then restart the NiFi on that node. It should join the cluster.
... View more
06-22-2017
03:19 PM
@riyer In the scenario I described, you could run the FetchFTP processor on all of the nodes, thus no bottleneck on the primary node.
... View more
06-20-2017
12:39 PM
@riyer For question 1, there are best practices depending on how data is being pulled/pushed into a cluster which leads to the answer for question 2. For question 2, if you configure the get processor to run on the primary node, there can only be one primary node at any time, so there would not be duplicate data. But a better solution that would take advantage of a cluster would be to use a ListFTP and FetchFtp processors. Run the ListFTP processor on the primary node and then distribute the list of files to all of the nodes in the cluster, via a remote process group back to itself, to a FetchFTP processor and that way each node will be pulling files from the source with no risk of duplicate data.
... View more