About MattWho

MattWho · ‎03-03-2017

@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

MattWho · ‎03-03-2017

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.

MattWho · ‎03-03-2017

@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

MattWho · ‎03-03-2017

@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

MattWho · ‎03-03-2017

@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

MattWho · ‎03-03-2017

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.

MattWho · ‎03-03-2017

@Sunile Manjee As part of the S2S protocol, the RPG will receive continuously get updated list of available peers (which includes load on peers in terms of total queued flowfiles) which it will store locally. It will then load-balanced based on that information. If for some reason it fails to get an update at any time it will continue to try and deliver and load-balance using the last list of known peers and loads. The RPG can get an updated list of available peers from any one of the target NiFi cluster's nodes. It only must get that list from the configured URL on the RPG the first time it connects. After that is has a list of peers it can get that info from. Thanks, Matt

MattWho · ‎03-03-2017

I don't know where HDFS files are placed in the sandbox, but I know you cannot copy the file from HDFS to NiFi from within Ambari. You will need to do this via a command/terminal window. you could use the "locate" command if you are running on linux and have the "mlocate" package installed. # yum -y install mlocate # updatedb # locate core-ste.xml

MattWho · ‎03-03-2017

@Martin van Husen The core-site.xml file is copied from your HDFS node to your NiFi node. You modify the local copy on NiFi as described above and point to this file using the the "Hadoop Configuration Resources" property in the NiFi HDFS processor.

MattWho · ‎03-03-2017

@Pradhuman Gupta Processors that support dynamic properties will include that information in their associated documentation. You can access processor documentation specific the NiFi release you are running via help found in the menu located in the upper right corner of the NiFi UI. You can also find the latest Apache NiFi version processor documentation here: https://nifi.apache.org/docs.html As an example of a processor that supports dynamic properties, look at GenerateFlowFile or UpdateAttribute. Thanks, Matt

Online	Offline
Last Visited	‎01-12-2026 12:56 PM

Member Since	‎07-30-2019 10:41 AM
Last Visited	‎01-12-2026 12:56 PM
Posts	3,419
Kudos received	1620

Cloudera Community

Re: Nifi 2.7.2 Start Problem

Re: Error importing NiFi workflow template from ve...

Re: Error importing NiFi workflow template from ve...

Re: How to elevate a default nifi user to admin - ...

Re: NiFi EnvokeHTTP - putting current date on HTTP...

Re: Unable to check access status in Apache Nifi(N...

Re: Unable to check access status in Apache Nifi(N...

Re: Unable to check access status in Apache Nifi(N...

Re: Unable to check access status in Apache Nifi(N...

Re: Unable to check access status in Apache Nifi(N...

Re: Load distribution of nifi flow files adding ne...

Re: Load distribution of nifi flow files adding ne...

Re: Failed to write to parent HDFS directory.

Re: Failed to write to parent HDFS directory.

Re: Can we add custom attribute in Apache NiFi on ...