I have tried this way as well, but now working. I really need help to know is this issue with the configuration or issue with the ports to communicate.
I have tried to replicate the same in my local laptop with default setup provided by apache ignite it is able to communicate. <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder"> <property name="addresses"> <list> <!-- In distributed environment, replace with actual host IP address. --> <value>17.20.70.18:47500..47509</value> <value>17.20.71.18:47500..47509</value> </list> </property> </bean> From: Abhijit Prusty [mailto:abhijitpru...@fico.com] Sent: Saturday, March 11, 2017 1:28 PM To: user@ignite.apache.org Subject: RE: Apache Ignite cluster with Multicast IP Startegy Hi Andrey, I tried the TcpDiscoveryVmIpFinder but in my case when I hit the node 1 I could see the cache count, where was NODE 2 show count 0. To help you understand better which would help in better way is we are in a TOOL where there is a deployment controller. We deploy to the main controller and it does the deployment to connected nodes. Now, If I observe the logs the war is getting deployed in both nodes, but I am absolutely not sure why the cache is not in sync between 2 nodes. If I run the cache builder REST call in both nodes then the cache is in sync. Do you have any other approach which could help to fix the issue. I had a word with the admin team, it is said as we are in subnet, all ports are open to communicate with each other. Hope to get additional help from you. Thanks, Abhijit From: Abhijit Prusty [mailto:abhijitpru...@fico.com] Sent: Saturday, March 11, 2017 11:46 AM To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: RE: Apache Ignite cluster with Multicast IP Startegy Hi, So the way I have used it not correct I guess. Mine is like this. We have a server like DEV 02 and it has 2 nodes, I assume it is in same machine. And below is the one I was using. I would try out your approach as well. <!-- Explicitly configure TCP discovery SPI to provide list of initial nodes. --> <property name="discoverySpi"> <bean class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> <property name="ipFinder"> <!-- Ignite provides several options for automatic discovery that can be used instead os static IP based discovery. For information on all options refer to our documentation: http://apacheignite.readme.io/docs/cluster-config --> <!-- Uncomment static IP finder to enable static-based discovery of initial nodes. --> <!--<bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">--> <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder"> <property name="addresses"> <list> <!-- In distributed environment, replace with actual host IP address. --> <value>127.0.0.1:47500..47509</value> </list> </property> </bean> </property> </bean> </property> From: Andrey Mashenkov [mailto:andrey.mashen...@gmail.com] Sent: Saturday, March 11, 2017 1:21 AM To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Re: Apache Ignite cluster with Multicast IP Startegy Hi, <bean class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> <property name="addresses"> <list> <!-- IP Address and optional port range of a remote node. --> <value>127.0.0.1:47500..47509</value> </list> </property> </bean> On Fri, Mar 10, 2017 at 9:15 PM, abhijitprusty <abhijitpru...@fico.com<mailto:abhijitpru...@fico.com>> wrote: Its on the same machine. I am not sure how to put these node IP in the configuration file properly. Could youu guide me please. From: vkulichenko [via Apache Ignite Users] [mailto:ml-node+<mailto:ml-node%2B>[hidden email]<http://user/SendEmail.jtp?type=node&node=11134&i=0>] Sent: Friday, March 10, 2017 8:52 PM To: Abhijit Prusty <[hidden email]<http://user/SendEmail.jtp?type=node&node=11134&i=1>> Subject: Re: Apache Ignite cluster with Multicast IP Startegy Are you running two nodes on different machines? It looks like multicast is not working in your network (which is often the case), and nodes do not discover each other because the only address provided is 127.0.0.1. I would recommend to try static configuration providing correct addresses: https://apacheignite.readme.io/docs/cluster-config#static-ip-based-discovery -Val ________________________________ If you reply to this email, your message will be added to the discussion below: http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-cluster-with-Multicast-IP-Startegy-tp11110p11124.html To unsubscribe from Apache Ignite cluster with Multicast IP Startegy, click here. NAML<http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately. ________________________________ View this message in context: RE: Apache Ignite cluster with Multicast IP Startegy<http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-cluster-with-Multicast-IP-Startegy-tp11110p11134.html> Sent from the Apache Ignite Users mailing list archive<http://apache-ignite-users.70518.x6.nabble.com/> at Nabble.com. -- Best regards, Andrey V. Mashenkov This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately. This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately. This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.