Sourav, Yes, the first thing that it will do is reach out to the node that you told it to contact and get a list of all other nodes in the cluster. It will then load balance across them, and handle failover, as it does today.
Thanks -Mark > On May 10, 2016, at 5:33 AM, Sourav Gulati <[email protected]> > wrote: > > Another question Mark, > > If I have provided URL of one of the node and that node goes down. Will it > still work? > > Regards, > Sourav Gulati > > -----Original Message----- > From: Sourav Gulati [mailto:[email protected]] > Sent: Tuesday, May 10, 2016 10:57 AM > To: [email protected] > Subject: RE: Reg: Nifi Clustering > > Thanks Mark for the information > > Regards, > Sourav Gulati > > -----Original Message----- > From: Mark Payne [mailto:[email protected]] > Sent: Monday, May 09, 2016 5:33 PM > To: [email protected] > Subject: Re: Reg: Nifi Clustering > > Sourav, > > Absolutely, Site-to-Site is a key enabler of NiFi and certainly will continue > to be supported. > Whereas right now you enter the URL of the NCM, you would simply enter the > URL of any of the nodes in the cluster. Your instance would then reach out to > that node and get a list of other nodes in the cluster. > > This will be similar to how the user will access the application, as well. In > 1.0, since there will be no NCM to connect to, you will be able to connect to > any node in the cluster, and it should be able to perform the necessary > functions. > > Thanks > -Mark > > >> On May 9, 2016, at 5:15 AM, Sourav Gulati <[email protected]> >> wrote: >> >> Hello Team, >> >> We are doing some poc with Nifi . IF successful, we may be using it in >> production some time in future. We are using site-to-site in our poc. As >> Joe, in the upcoming 1.0 release work is being done to eliminate this notion >> of master/slave altogether. >> >> Will site-to-site be still supported? Reason I am asking this is currently >> while configuring site-to-site we need to provide URL of NCM in Remote >> process Group. >> >> >> Regards, >> Sourav Gulati >> >> -----Original Message----- >> From: Matthew Clarke [mailto:[email protected]] >> Sent: Tuesday, May 03, 2016 4:41 PM >> To: [email protected] >> Subject: RE: Reg: Nifi Clustering >> >> Sourav, >> A single instance of NiFi cannot be both a NCM and a Node at the same time. >> In order to have both a NCM and a Node on a single server, you will need to >> install two copies of NiFi. One will be configured to be the NCM while the >> other is configured to be the Node. As Joe pointed out, these two instance >> of NiFi cannot share any listening ports (HTTP or S2S ports) in their >> configs. >> >> Matt >> On May 3, 2016 2:03 AM, "Sourav Gulati" <[email protected]> wrote: >> >> Hi Joe, >> >> This is what I am getting while running both master and node >> >> IllegalStateException: Application may be configured as a cluster >> manager or a node, but not both >> >> >> >> Regards, >> Sourav Gulati >> >> -----Original Message----- >> From: Joe Witt [mailto:[email protected]] >> Sent: Monday, May 02, 2016 6:45 PM >> To: [email protected] >> Subject: Re: Reg: Nifi Clustering >> >> Sourav, >> >> The installation procedure does not differ. However, you do need to be >> careful to ensure you're not trying to use the same ports for both the >> master and the node. >> >> If you're having trouble go ahead and send some of the configuration details >> over and someone can try to assist. >> >> Thanks >> Joe >> >> On Mon, May 2, 2016 at 9:05 AM, Sourav Gulati >> <[email protected]> >> wrote: >>> Hello Joe, >>> >>> Could you please provide steps of creating cluster on single node in >> current version? >>> >>> Regards, >>> Sourav Gulati >>> >>> -----Original Message----- >>> From: Joe Witt [mailto:[email protected]] >>> Sent: Monday, May 02, 2016 6:28 PM >>> To: [email protected] >>> Subject: Re: Reg: Nifi Clustering >>> >>> Sourav, >>> >>> Yes. And in the upcoming 1.0 release work is being done to eliminate >> this notion of master/slave altogether and move to instead that at any time >> any node can carry the responsibility of being a coordinator for the cluster. >>> >>> Thanks >>> Joe >>> >>> On Mon, May 2, 2016 at 8:49 AM, Sourav Gulati >>> <[email protected]> >> wrote: >>>> Hi Team, >>>> >>>> While creating Nifi Cluster, Can I run master and slave on same node? >>>> >>>> Regards, >>>> Sourav Gulati >>>> >>>> >>>> ________________________________ >>>> >>>> >>>> >>>> >>>> >>>> >>>> NOTE: This message may contain information that is confidential, >> proprietary, privileged or otherwise protected by law. The message is >> intended solely for the named addressee. If received in error, please >> destroy and notify the sender. Any use of this email is prohibited when >> received in error. Impetus does not represent, warrant and/or guarantee, >> that the integrity of this communication has been maintained nor that the >> communication is free of errors, virus, interception or interference. >>> >>> ________________________________ >>> >>> >>> >>> >>> >>> >>> NOTE: This message may contain information that is confidential, >> proprietary, privileged or otherwise protected by law. The message is >> intended solely for the named addressee. If received in error, please >> destroy and notify the sender. Any use of this email is prohibited when >> received in error. Impetus does not represent, warrant and/or guarantee, >> that the integrity of this communication has been maintained nor that the >> communication is free of errors, virus, interception or interference. >> >> ________________________________ >> >> >> >> >> >> >> NOTE: This message may contain information that is confidential, >> proprietary, privileged or otherwise protected by law. The message is >> intended solely for the named addressee. If received in error, please >> destroy and notify the sender. Any use of this email is prohibited when >> received in error. Impetus does not represent, warrant and/or guarantee, >> that the integrity of this communication has been maintained nor that the >> communication is free of errors, virus, interception or interference. >> >> ________________________________ >> >> >> >> >> >> >> NOTE: This message may contain information that is confidential, >> proprietary, privileged or otherwise protected by law. The message is >> intended solely for the named addressee. If received in error, please >> destroy and notify the sender. Any use of this email is prohibited when >> received in error. Impetus does not represent, warrant and/or guarantee, >> that the integrity of this communication has been maintained nor that the >> communication is free of errors, virus, interception or interference. > > > ________________________________ > > > > > > > NOTE: This message may contain information that is confidential, proprietary, > privileged or otherwise protected by law. The message is intended solely for > the named addressee. If received in error, please destroy and notify the > sender. Any use of this email is prohibited when received in error. Impetus > does not represent, warrant and/or guarantee, that the integrity of this > communication has been maintained nor that the communication is free of > errors, virus, interception or interference. > > ________________________________ > > > > > > > NOTE: This message may contain information that is confidential, proprietary, > privileged or otherwise protected by law. The message is intended solely for > the named addressee. If received in error, please destroy and notify the > sender. Any use of this email is prohibited when received in error. Impetus > does not represent, warrant and/or guarantee, that the integrity of this > communication has been maintained nor that the communication is free of > errors, virus, interception or interference.
