> > I mainly want to know whether the detached need would join the cluster > automatically after the network is back or not? > *need = node
I tests such a situation, and found that the detached node is not joining the cluster. Instead it produces following errors: 2018-08-29 12:35:25.625 ERROR 3129 --- [5%igniteserver%] > .s.d.t.i.m.TcpDiscoveryMulticastIpFinder : Failed to request nodes > addresses. > java.net.SocketException: Cannot assign requested address (Error setting > socket option) at java.net.PlainDatagramSocketImpl.socketSetOption0(Native Method) > ~[na:1.8.0_151] at > java.net.PlainDatagramSocketImpl.socketSetOption(PlainDatagramSocketImpl.java:74) > ~[na:1.8.0_151] at > java.net.AbstractPlainDatagramSocketImpl.setOption(AbstractPlainDatagramSocketImpl.java:309) > ~[na:1.8.0_151] at java.net.MulticastSocket.setInterface(MulticastSocket.java:471) > ~[na:1.8.0_151] at > org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder.requestAddresses(TcpDiscoveryMulticastIpFinder.java:565) > [ignite-core-2.7.0-SNAPSHOT.jar!/:2.7.0-SNAPSHOT] at > org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder.access$700(TcpDiscoveryMulticastIpFinder.java:80) > [ignite-core-2.7.0-SNAPSHOT.jar!/:2.7.0-SNAPSHOT] at > org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder$AddressReceiver.body(TcpDiscoveryMulticastIpFinder.java:780) > [ignite-core-2.7.0-SNAPSHOT.jar!/:2.7.0-SNAPSHOT] at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > [ignite-core-2.7.0-SNAPSHOT.jar!/:2.7.0-SNAPSHOT] > 2018-08-29 12:35:25.827 ERROR 3129 --- [5%igniteserver%] > .s.d.t.i.m.TcpDiscoveryMulticastIpFinder : Failed to request nodes > addresses. > java.net.SocketException: Cannot assign requested address (Error setting > socket option) at java.net.PlainDatagramSocketImpl.socketSetOption0(Native Method) > ~[na:1.8.0_151] at > java.net.PlainDatagramSocketImpl.socketSetOption(PlainDatagramSocketImpl.java:74) > ~[na:1.8.0_151] at > java.net.AbstractPlainDatagramSocketImpl.setOption(AbstractPlainDatagramSocketImpl.java:309) > ~[na:1.8.0_151] at java.net.MulticastSocket.setInterface(MulticastSocket.java:471) > ~[na:1.8.0_151] at > org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder.requestAddresses(TcpDiscoveryMulticastIpFinder.java:565) > [ignite-core-2.7.0-SNAPSHOT.jar!/:2.7.0-SNAPSHOT] at > org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder.access$700(TcpDiscoveryMulticastIpFinder.java:80) > [ignite-core-2.7.0-SNAPSHOT.jar!/:2.7.0-SNAPSHOT] at > org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder$AddressReceiver.body(TcpDiscoveryMulticastIpFinder.java:780) > [ignite-core-2.7.0-SNAPSHOT.jar!/:2.7.0-SNAPSHOT] at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > [ignite-core-2.7.0-SNAPSHOT.jar!/:2.7.0-SNAPSHOT] Any idea how to fix this? I also tried with the flag "-Djava.net.preferIPv4Stack=true" but it didn't make a difference. > On Tue, Aug 28, 2018 at 9:04 PM Lokesh Sharma <[email protected]> wrote: > I mainly want to know whether the detached need would join the cluster > automatically after the network is back or not? > > On Tue, Aug 28, 2018, 8:09 PM Lokesh Sharma <[email protected]> > wrote: > >> What is the expected behaviour of Ignite when a node is unreachable from >> other nodes of the cluster due to *network failure *(and not due to node >> failure), and after a while the node is again accessible from the cluster? >> In other words, one node gets dropped from the cluster due to network >> failure and then again joins the cluster but it does not reboots. >> >
