Hello! Why would you want to do that?
Regards, -- Ilya Kasnacheev вт, 2 июн. 2020 г. в 08:32, Kamlesh Joshi <kamlesh.jo...@ril.com>: > Thanks Alex. Actually, I don't want to start two different clusters on > same machine, rather am looking to have a different networks for Ignite > clients discovery and internal communication. > > Not sure whether we can achieve this using below. > > Thanks and Regards, > Kamlesh Joshi > > -----Original Message----- > From: akorensh <alexanderko...@gmail.com> > Sent: 01 June 2020 23:20 > To: user@ignite.apache.org > Subject: [External]Re: Segregating Ignite client discovery and heartbeat > exchange on different networks > > The e-mail below is from an external source. Please do not open > attachments or click links from an unknown or suspicious origin. > > Hi, > An example of isolated cluster is provided here: > > https://apacheignite.readme.io/docs/tcpip-discovery#isolated-ignite-clusters-on-same-set-of-machines > > You can try binding specific IPs to a different networks > use: CommunicationSpi: > > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.html#setLocalAddress-java.lang.String- > > Discovery Spi: > > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.html#setLocalAddress-java.lang.String- > > Thanks, Alex > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > "Confidentiality Warning: This message and any attachments are intended > only for the use of the intended recipient(s). > are confidential and may be privileged. If you are not the intended > recipient. you are hereby notified that any > review. re-transmission. conversion to hard copy. copying. circulation or > other use of this message and any attachments is > strictly prohibited. If you are not the intended recipient. please notify > the sender immediately by return email. > and delete this message and any attachments from your system. > > Virus Warning: Although the company has taken reasonable precautions to > ensure no viruses are present in this email. > The company cannot accept responsibility for any loss or damage arising > from the use of this email or attachment." > >
