Member since
07-30-2019
3404
Posts
1621
Kudos Received
1003
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 174 | 12-05-2025 08:25 AM | |
| 314 | 12-03-2025 10:21 AM | |
| 586 | 11-05-2025 11:01 AM | |
| 437 | 11-05-2025 08:01 AM | |
| 892 | 11-04-2025 10:16 AM |
06-01-2017
11:45 AM
@Oleksandr Solomko There must be something else going on in your system. Are you seeing any WARN or ERROR log messages in your nifi logs? Did you run out of disk space at any time? Are you seeing any Out Of Memory (OOM) errors in your nifi logs? Thanks, Matt
... View more
06-01-2017
11:23 AM
@Simran Kaur I had a feeling your issue was related to a missing config. Glad to hear you got it working. If this answer addressed your original question, please mark it as accepted. As far as your other question goes, I see you already started a new question (https://community.hortonworks.com/questions/105720/nifi-stream-using-listenhttp-processor-creates-too.html). That is the correct approach in this forum, we want to avoid asking unrelated questions in the same post. I will have a look at that post as well. Thank you, Matt
... View more
06-01-2017
11:12 AM
@Oleksandr Solomko
What version of NiFi are you running? Are you seeing any Out Of Memory errors in your nifi logs? This could be causing issues with emptying the queue. The fastest way to clear this specific queue now might be to stop both the SplitAVRO and PublishKafka processors. Add an UpdateAttribute processor to your graph with the success relationship set to auto-terminate. Select the queued connection and drag the blue dot (near the arrow end of the connection) to the update Attribute processor. Start the updateAttribute processor and it will start auto-terminating FlowFiles form this connection in batches. Thanks, Matt
... View more
06-01-2017
11:04 AM
1 Kudo
@Simran Kaur I see from your screenshot that your putHDFS processor is producing bulletins (Red square in upper right corner). If you float your cursor over this red square you will see the bulletin displayed. You can also look for this same error in the nifi-app.log. In many cases the error will be followed by a full stack trace in the nifi-app.log. That stack trace and the error log line may explain what you issue is here. If this does not help, please share your putHDFS processor configuration. Thanks, Matt
... View more
05-31-2017
09:36 PM
No problem... as soon as you added that you were running HDF 2.1.2, it helped.
... View more
05-31-2017
08:46 PM
@Oliver Meyn You have run in to the following bug: https://issues.apache.org/jira/browse/NIFI-3664 The good news is that the fix for this bug is part of HDF 2.1.3. Thank you, Matt
... View more
05-31-2017
04:49 PM
2 Kudos
@Oliver Meyn In NiFi cluster, the time that is displayed could come form anyone of the connected nodes. It is important to use NTP on every node in your NiFi cluster to make sure that time stays in sync. As far as timezone differences go, Make sure the symlink for /etc/localtime is pointing at the same /usr/share/timezone/... file on every one of you nIfi nodes. Run the "date --utc" command on all your nodes and compare it to both of the following commands: zdump /usr/share/zoneinfo/EST
zdump /usr/share/zoneinfo/US/Eastern If you are looking for EDT time you need to make sure that the symlink for /etc/localtime is point to the following on all yoru nodes: lrwxrwxrwx. 1 root root 25 Dec 1 2014 localtime -> ../usr/share/zoneinfo/US/Eastern Thanks, Matt
... View more
05-31-2017
01:51 PM
3 Kudos
@Simran Kaur All ports 1024 and below are considered reserved as privileged ports and can be only used/bound to by process run by the root user. NiFi can use these ports if it is running as the root user. The alternative is to setup your ListenHTTP processor to run on a non privileged port and then set up port forwarding in your iptables to redirect incoming requests to a privileged port to that non privileged port you are using in NiFi: iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 8081 Thanks,
... View more
05-31-2017
01:44 PM
2 Kudos
@Richard Corfield You can get GC output logs out of NiFi by adding the following lines to NiFi's bootstrap.conf file: java.arg.20=-XX:+PrintGCDetails
java.arg.21=-XX:+PrintGCTimeStamps
java.arg.22=-XX:+PrintGCDateStamps
java.arg.23=-Xloggc:<file>
The last entry allows you to specific a separate log file for this output to be written in to rather then stdout. Thanks, Matt
... View more
05-31-2017
12:58 PM
@Joshua Adeleke Are you able to add new controller services?
... View more