Hello! It is currently delayed, but it should get there eventually.
You can watch https://lists.apache.org/thread.html/rfd2346f83e28300d687f331afebcb9233265ed10911746d876970106%40%3Cdev.ignite.apache.org%3E or try a nightly build: https://ci.ignite.apache.org/buildConfiguration/Releases_NightlyRelease_RunApacheIgniteNightlyRelease?branch=ignite-2.9&buildTypeTab=overview&mode=builds Regards, -- Ilya Kasnacheev вт, 8 сент. 2020 г. в 08:35, Kamlesh Joshi <[email protected]>: > Thanks for the update Ilya. > > > > You mean in this scenario, thin clients will work properly (will be > connecting via public IP instead of private). > > > > And do you have any idea when Ignite 2.9 version will be released ? > > > > *Thanks and Regards,* > > *Kamlesh Joshi* > > > > *From:* Ilya Kasnacheev <[email protected]> > *Sent:* 07 September 2020 19:52 > *To:* [email protected] > *Subject:* Re: [External]Re: Private network setup for server nodes in > ignite cluster > > > > The e-mail below is from an external source. Please do not open > attachments or click links from an unknown or suspicious origin. > > Hello! > > > > In Apache Ignite, thick clients are part of topology, and as such they > will use the same addresses as server nodes do. In your case that's private > address. > > > > Upcoming 2.9 will probably feature "communication by discovery" mode where > this restriction is relaxed. > > > > You can use all kinds of thin clients (REST, JDBC, etc) by using public > addresses. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пн, 7 сент. 2020 г. в 17:06, Kamlesh Joshi <[email protected]>: > > Hi Ilya, > > > > Any updates on this please? > > > > *Thanks and Regards,* > > *Kamlesh Joshi* > > > > *From:* Kamlesh Joshi > *Sent:* 04 September 2020 17:33 > *To:* [email protected] > *Subject:* RE: [External]Re: Private network setup for server nodes in > ignite cluster > > > > Hi Ilya, > > > > We have tried the setup by putting public ips for discoverySpi and private > ips for CommunicationSpi. > > > > *Cluster is up and running but clients not able to connect cluster*. > IgniteVisor able to connect to cluster as it is on one of the server node, > we are able to see clients connected to cluster in visor. But below error > is getting at client side while connecting. > > > > class org.apache.ignite.IgniteCheckedException: Failed to connect to node > (is node still alive?). Make sure that each ComputeTask and cache > Transaction has a timeout set in order to prevent parties from waiting > forever in case of network issues > [nodeId=51868027-53dc-47bc-9d47-b6ec77b9edf5, addrs=[/PRIVATEIP:47100]] > > at > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:3459) > > at > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2987) > > at > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2870) > > at > org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2713) > > > > Below is the server config used while starting server nodes. > > > > <property name="discoverySpi"> > > <bean > > > class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> > > <property name="ipFinder"> > > <bean > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> > > <property name="addresses"> > > <bean > class="org.springframework.util.StringUtils" > > > factory-method="commaDelimitedListToSet"> > > <constructor-arg type="java.lang.String" > > > value="${PublicIPAddresses}" /> > > </bean> > > </property> > > </bean> > > </property> > > </bean> > > </property> > > <property name="communicationSpi"> > > <bean > class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi"> > > <property name="localAddress" value="PrivateIP"/> > > </bean> > > </property> > > > > > > *Thanks and Regards,* > > *Kamlesh Joshi* > > > > *From:* Ilya Kasnacheev <[email protected]> > *Sent:* 18 August 2020 16:05 > *To:* [email protected] > *Subject:* [External]Re: Private network setup for server nodes in ignite > cluster > > > > The e-mail below is from an external source. Please do not open > attachments or click links from an unknown or suspicious origin. > > Hello! > > > > You need to do setLocalHost(private IP) on all of your server nodes. Or > use IGNITE_LOCAL_HOST system property/environment variable. > > > > For client connector/REST/etc, you can specify public IP explicitly. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 18 авг. 2020 г. в 09:21, Trilok Joshi <[email protected]>: > > Hi, > > > > We want to configure private network for server nodes in ignite cluster so > that all communication among the server nodes happen using the network like > handshake. And also clients will use different network to connect to the > cluster and serving the requests > > > > Could you please help us how to configure the cluster setup. > > > > Regards, > > Gangaiah > > > "*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." > > > "*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." > > > "*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." >
