Hi, You should set MulticastGroup and MulticastPort to enable muticast. See [1] and [2]
[1] https://apacheignite.readme.io/docs/cluster-config#multicast-based-discovery [2] https://ignite.apache.org/releases/mobile/org/apache/ignite/spi/discovery/tcp/ipfinder/multicast/TcpDiscoveryMulticastIpFinder.html On Fri, Mar 10, 2017 at 4:54 PM, abhijitprusty <abhijitpru...@fico.com> wrote: > I am using the below config for the multicast but seems its not forming the > topology. I am using a JBOSS server which is clustered. > > <bean > class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast. > TcpDiscoveryMulticastIpFinder"> > <property name="addresses"> > <list> > > <value>127.0.0.1:47500..47509</value> > </list> > </property> > </bean> > > When I see in the logs both node behaves like its a new server, the server > count is not increasing. > Node 1 - Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, > heap=18.0GB] > Node 2 - Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, > heap=18.0GB] > > If I fire request on each node, one node says the ignite instance is not > null, and the node 2 shows below error > Exception in duplicate check : Error: Ignite instance with provided name > doesn't exist. Did you call Ignition.start(..) to start an Ignite instance? > [name=null] > > I need really help here to get this issue fixed. > > > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Apache-Ignite-cluster-in-with-MulticastIP-tp11110.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best regards, Andrey V. Mashenkov
