Member since
07-30-2019
3133
Posts
1564
Kudos Received
909
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
129 | 01-09-2025 11:14 AM | |
800 | 01-03-2025 05:59 AM | |
415 | 12-13-2024 10:58 AM | |
453 | 12-05-2024 06:38 AM | |
368 | 11-22-2024 05:50 AM |
03-06-2017
03:30 PM
@Gaurav Jain Please provide full use case and examples. It is difficult to provide assistance without the details. The more the better.
... View more
03-06-2017
03:28 PM
4 Kudos
@Mark Heydenrych While I like the idea, there is currently no way to have a log message written to a FlowFiles attribute upon routing to a failure relationship. You may want to open an Apache NiFi Jira around this idea. Typically the "failure" relationship is routed back on the source processor so that multiple attempts can be made to deliver the file. In cases like network hicups, duplicate files, etc. this makes a lot of sense. When dealing with processor config failures, permissions issues, etc. the file will never be successful. You could set up a failure count loop. This loop would create an attribute on FlowFiles that are routed to "failure" and continue to loop them back on PutHDFS until the count has reached a configured number. Once that count is reached, the FlowFiles could be routed out of the loop. You could then send a notification via putEmail of the failed FlowFile for user investigation. Here is a link to a retry count loop flow NiFi template: https://cwiki.apache.org/confluence/download/attachments/57904847/Retry_Count_Loop.xml?version=1&modificationDate=1433271239000&api=v2 Thanks, Matt
... View more
03-06-2017
03:13 PM
4 Kudos
@adrian white You can use the MergeContent processor followed by a RouteOnAttribute processor to accomplish what you are looking to do. The MergeContent processor writes an attribute named "merge.count" to the FlowFile containing all your merged source flowfiles. - Set Min entries to "50" - Set Max Entries to "50" - Set Max Bin age to "1 min" The bin age timer is trigger once the very first FlowFile is added. At the end of 1 min or 50 FlowFiles (whichever occurs first) the Bin will be merged. Connect the "merged" relationship to a RouteOnAttribute processor that checks the "merge.count" on the merged FlowFiles to verify that they contain 50 entries. "small" will become a new relationship to the RouteOnAttribute processor. - Auto-terminate the "small" relationship so that any merged FlowFile with fewer then 50 entries is deleted. - Route the "unmatched" relationship on down the rest of your dataflow. Thanks, Matt
... View more
03-03-2017
07:51 PM
Is there anything in the nifi-user.log when you try to access the https web address?
I also noticed the URLs are for 10.x.x.x web addresses. Are these address reachable from the system where you have your web browser loaded?
Can you post a screenshot of your browser when you try to access the https web address? Matt
... View more
03-03-2017
07:37 PM
@Ayaskant Das Now we know that your NiFi is up and running. We also know that it has been configured to run securely over https.
After being secured you will not be able to access it over http. Https access will only work if user authentication is successful which comes full circle to my initial response. Here are a few links to assist you there: https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#user-authentication https://community.hortonworks.com/articles/17293/how-to-create-user-generated-keys-for-securing-nif.html
Thanks, Matt
... View more
03-03-2017
07:13 PM
those are normal... it is still starting. it may appear to stall at certain points during startup... Di you perhaps issue a shutdown command before it ever finished actually starting? keep tailing the log until you see it either show the URL line or it shuts down again on its own. This may taken several minutes.
perhaps sharing your nifi-app.log after is fails again will help.
... View more
03-03-2017
06:54 PM
@Ayaskant Das So your nifi shut back down because of some error that occurred during startup. That error will be in the nifi-app.log somewhere above the lines you posted. It will likely have a full stack trace with the error that includes the cause. Thanks, Matt
... View more
03-03-2017
06:30 PM
@Ayaskant Das When you start NiFi, the bootstrap.conf file will show that the bootstrap is listening on port .... but this does not mean the application has fully started yet. The browser will not be available until it has. if you tail -F nifi-app.log you can watch all the things that happen during application startup. Check your nifi-app.log for reported issues and look for the following line being outputted: org.apache.nifi.web.server.JettyServer NiFi has started. The UI is available at the following URLs: following this line will be additional lines showing the full URL(s). Until this line is output the browser will still be unavailable. Thanks, Matt
... View more
03-03-2017
06:08 PM
@Ayaskant Das Is your NiFi instance secured?
If so, how are you configured to authenticate users who are accessing the URL? By default NiFi will look for a users SSL certificate in the connection for authentication. If none is provided and no other authentication method has been configured in your NiFi, the connection will just get closed. Thanks, Matt
... View more
03-03-2017
05:18 PM
Yes, nodes can be added in real time to an existing niFi Cluster. Yes, the RPG is constantly get an updated list of nodes in the target cluster. That includes if a node was added or removed.
... View more