Hi, I remember having the same problem
In my case, I had to assign correct hostnames for each node in the cluster In conf/nifi.properties, NCM node: nifi.web.http.host=vbox1 nifi.web.http.port=7070 Slave node: nifi.web.http.host=vbox2 (leaving this blank makes NiFi bind to localhost) nifi.web.http.port=7272 Let me know how your setup is and I'll try to check also. Owie ----- Original Message ----- From: "Corey Flowers" <[email protected]> To: [email protected] Sent: Friday, March 20, 2015 4:51:27 AM Subject: Re: Having isues with NiFi cluster Have you verified that all the management ports are open? It maybe waiting on a response from one of the nodes. If you would like, you could send me the app and wrapper log and I will take a look. Sent from my iPhone > On Mar 19, 2015, at 7:05 AM, Kalisz, John T. <[email protected]> wrote: > > I set up a NiFi cluster based on the following Wiki: > > https://kisstechdocs.wordpress.com/2015/01/15/simple-tasks-in-nifi-creating-a-super-simple-cluster/ > > It is a three node cluster with one node (server) set up as the cluster > manager and two other servers set up as nodes. > When I start the cluster everything appears to work. There are no discernable > errors in the log files and the two nodes are sending heartbeats to the > master. When I try bring up the NiFi index page, I simply see a "loading" > icon that never goes away. > I also noticed that the heartbeats from the nodes are being generated at a > significantly higher rate than the default setting of 5 seconds. > > Any guidance would be appreciated. > > John T. Kalisz > General Dynamics Mission Systems > > Office 413-494-3376 | Cell 413-822-1883 | > [email protected]<mailto:[email protected]> > > This message and/or attachments may include information subject to GD > Corporate Policies 07-103 and 07-105 and is intended to be accessed only by > authorized recipients. Use, storage and transmission are governed by General > Dynamics and its policies. Contractual restrictions apply to third parties. > Recipients should refer to the policies or contract to determine proper > handling. Unauthorized review, use, disclosure or distribution is > prohibited. If you are not an intended recipient, please contact the sender > and destroy all copies of the original message. >
