I've found. TcpDiscoveryNode try to resolve sockAddrs in readExternal
method from hostNames (first) and addrs (second). TcpDiscoverySpi fills
hostNames for node with local hostnames. And of course new client node
can resolve only local hostname. In my case resolution of other node's
hostnames
I've found. TcpDiscoveryNode try to resolve sockAddrs in readExternal
method from hostNames (first) and addrs (second). TcpDiscoverySpi fills
hostNames for node with local hostnames. And of course new client node
can resolve only local hostname. In my case resolution of other node's
hostnames
After reconnect unmarshalling of TcpDiscoveryNodeAddedMessage takes 20
seconds:
2018-11-12 14:10:36.105 ERROR 10 --- [-sock-reader-#3]
o.a.ignite.marshaller.jdk.JdkMarshaller : Unmarshall 1
2018-11-12 14:10:36.107 ERROR 10 --- [-sock-reader-#3]
o.a.ignite.marshaller.jdk.JdkMarshaller : Unmarshall
Hi, Andrei. Thank you for reply.
I have found that problem is in unmarshalling:
2018-11-12 13:18:24.375 INFO 10 --- [-sock-reader-#3]
o.a.i.spi.discovery.tcp.TcpDiscoverySpi : 1
2018-11-12 13:18:24.375 DEBUG 10 --- [o-msg-worker-#4]
o.a.i.spi.discovery.tcp.TcpDiscoverySpi : Received metrics
Hi,
Could you please attach the XML configurations of your client and server
nodes and logs?
BR,
Andrei
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
