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.
