Member since
07-30-2019
613
Posts
194
Kudos Received
91
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
226 | 10-05-2021 01:53 PM | |
7575 | 09-23-2019 06:03 AM | |
2829 | 05-04-2019 08:42 PM | |
517 | 06-11-2018 12:45 PM | |
6128 | 06-04-2018 01:11 PM |
04-18-2017
09:31 PM
@Raj B Are you using SFTP to push data?
... View more
04-18-2017
07:15 PM
@Grady R Why not use NiFi's site-to-site capability to transfer the files?
... View more
04-18-2017
07:13 PM
@Raj B Is it possible to have NiFi pull the data from the source?
... View more
04-18-2017
05:30 PM
@Raj B
Can java be installed on the load balancer? If so, I would install NiFi on the load balancer and then just add a Remote process group to the NiFi instance on the load balancer and let NiFi handle the load balancing.
... View more
04-18-2017
03:49 PM
1 Kudo
@Ed Prout One way around the issue, is to monitor the success relationship out of the GetSplunk processor using the MonitorActivity processor. If data does not pass through in a set time period, the the MonitorActivity processor generates an "inactive" flow file and this can be used as a trigger for an ExecuteScript processor which would run a curl script to restart the processor. Not an elegant solution, but it should work.
... View more
04-18-2017
03:33 PM
@Gu Gur You could you the ExecuteScript processor, but that would probably be more work than just doing it manually since it is only two nodes you are adding. I am assuming you have not secured the cluster. You could just copy the conf directory over to the new nodes, and then update the all entries to match the name of the new host. For example, assuming the current nodes are node1.localdomain, node2.localdomain and node3.localdomain, then copy node3's conf directory to a new node you want to add, you could just change everywhere you have node3 to node4, or whatever is the new node system name. Are you following me?
... View more
04-18-2017
01:45 PM
2 Kudos
@Harish S Add the line "useTicketCache=true" to the jaas.conf file. What are the differences between the dev and test environments? Are you using the same KDC server? Same kafka brokers?
... View more
04-18-2017
12:24 PM
@Harish S If you run the klist command as the user running NiFi, what do you see?
... View more
04-18-2017
11:58 AM
2 Kudos
@Jatin Kheradiya Currently, when any changes are made to the nifi.properties file, NiFi does need to be restarted. There are new features coming in future releases that will not require a restart of NiFi.
... View more
04-17-2017
07:53 PM
@Raj B I would agree. Are you running the curl commands on the same system with the NiFi instance you are running the curl command against? Try running the curl commands from a remote system that can reach the NiFi instance. Also, make sure you are not logged into the NiFi instance, via the UI, while you are running the curl commands, I have found that can cause some issues.
... View more
04-17-2017
06:18 PM
@Raj B Try something like this: curl 'https://<nifi-server>:8077/nifi-api/system-diagnostics' -H 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJjbj1SUkJvbGxhLG91PURhdGEgTWFuYWdlbWVudCxvdT1QT0Usb3U9UGVvcGxlLGRjPW1kYW5kZXJzb24sZGM9ZWR1IiwiaXNzIjoiTGRhcFByb3ZpZGVyIiwiYXVkIjoiTGRhcFByb3ZpZGVyIiwicHJlZmVycmVkX3VzZXJuYW1lIjoiUlJCb2xsYSIsImtpZCI6MzMsImV4cCI6MTQ5MjA5OTcyNiwiaWF0IjoxNDkyMDkyNTI2fQ.xIViD0Ea_fok6qV5ghnf65FPbO9Reh_MQxVG2Q1krl4%' --compressed --insecure --tlsv1.2 In addition, make sure the user you are accessing the UI with has the correct policies to access to the system-diagnostics.
... View more
04-17-2017
05:33 PM
@Gu Gur No, you only have to configure the two new nodes to be part of the cluster that is already running. Make sure to configure to use the same root node in zookeeper, set this property nifi.zookeeper.root.node, to the same values that the other three nodes are using, and of course configure the cluster node properties.
... View more
04-17-2017
02:17 PM
1 Kudo
@Avish Saha If you right click on the incoming connection a pop-up menu will appear: Select List queue, then you can look at the data the ReplaceText is trying to process. It looks like the end of the file being split may have incomplete lines?
... View more
04-17-2017
01:37 PM
2 Kudos
@Gu Gur If you configure the two nodes the same way as the current three nodes in the cluster, they should "ask to join" automatically. Which version of NiFi are you using?
... View more
04-17-2017
01:31 PM
2 Kudos
@Prakhar Agrawal With the NiFi 1.x baseline, zookeeper is a fundamental part of the NiFi cluster. It is used to automatically determine the cluster coordinator as well as communication within the cluster. With the NiFi 0.x baseline, the cluster has an cluster manager which serves a similar role and did not use zookeeper at all. So, if you do not want to use zookeeper, you will have to use a 0.x baseline version of NiFi.
... View more
04-17-2017
01:07 PM
2 Kudos
@Eric Lloyd You don't have to uninstall NiFi to start clean. Just clean out all the directories under the content, flowfile, provenance repositories and you should be good to go. When you ran out of disk space it corrupted the flowfile repository, which is how NiFi knows the status of the flow files in the graph. If possible, I would recommend at a minimum of moving the flowfile repository to it's own disk partition.
... View more
04-17-2017
12:55 PM
@Maxime Lézier Which version of NiFi are you using? How many concurrent tasks does the ListFTP processor have configured?
... View more
04-17-2017
12:50 PM
1 Kudo
@Raj B
I have found, depending on some of the default system settings, that I need an additional flag on the subsequent curl commands after getting the token. Try adding --tlsv1.2 after the compressed and insecure flags. Also, you will still need the Content-type information on subsequent curl commands.
... View more
04-13-2017
12:42 PM
@rm -rf /* So, if it was always able to start NiFi. When did it stop working and why did you need to restart NiFi?
... View more
04-13-2017
12:08 AM
@rm -rf /* Was Ambari ever able to start NiFi, or did it always fail?
... View more
04-12-2017
01:48 PM
@Ray Deng What value is in the property nifi.security.user.login.identity.provider
... View more
04-12-2017
01:34 PM
@Ray Deng What version of IE are you using and do you have another browser you are able to try?
... View more
04-12-2017
01:27 PM
@subash sharma The Rest API documentation will be found at the URL: https://nifi-host:port/nifi-docs/rest-api Just replace the the nifi-host and port values with your information.
... View more
04-12-2017
01:12 PM
@Ray Deng That warning is normal, not the issue. If there is nothing else in the user log, that means you are not even getting to NiFi. Is port 7071 open? What URL are you using? The same on that is in the app log? https://spark-nn01.local:7071/nifi? Can the system you are launching IE from resolve the hostname to an IP address? Did you generate a user certificate to load into the IE browser?
... View more
04-12-2017
12:18 PM
1 Kudo
@Emmanouil Petsanis
The DuplicateFlowFile processor will do what you need. FYI, the duplicated flow files will have identical file names as well the other attributes.
... View more
04-12-2017
01:24 AM
2 Kudos
@subash sharma Here is the command you need, just fill in your appropriate values: curl 'https://nifi-host:port/nifi-api/access/token' -H 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' --data 'username=ldap-username&password=ldap-password' --compressed —insecure And there you go, this will return the token you need. The subsequent curl commands will need the token returned as part of the command: -H 'Authorization: Bearer token-returned'
... View more
04-11-2017
07:35 PM
1 Kudo
@Ray Deng Did you generate a user certificate to load into the IE browser? Look in the nifi-user.log file and look for any errors.
... View more
04-11-2017
06:41 PM
2 Kudos
@subash sharma Here is the format of the command you need to get a token: curl 'https://nifi-host:port/nifi-api/access/token' -H 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' --data 'username=ldap-username&password=ldap-password' --compressed —insecure Then add the following to all of your subsequent curl commands -H 'Authorization: Bearer token-returned’
... View more
04-11-2017
03:22 PM
@Anthony Schuhl Try adding the following flags to your second curl command: --insecure --tlsv1.2
... View more
- « Previous
- Next »