Re: The wrong sockAddrs are registered, and the cluster is broken when it tries to connect it occasionally.

2018-02-27 Thread ezhuravlev 
If it really starts to use addresses other that pre-configured, you should
share your configurations and full logs from all nodes, the community will
check it.

Evgenii



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: The wrong sockAddrs are registered, and the cluster is broken when it tries to connect it occasionally.

2018-02-04 Thread dark 
We have confirmed that only 10.xxx.xxx.x has been registered by updating
according to the information you have given.

Which of the addresses registered with sockAddrs will Ignite use to connect
to? After connection is disconnected, it seems that there is a case that I
am trying to renew connection through Docker IP.

Thank you. 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

The wrong sockAddrs are registered, and the cluster is broken when it tries to connect it occasionally.

2018-02-01 Thread dark 
Cluster was broken some time ago. In my opinion, it seems to use Docker IP,
not normal IP, in communication. Is it possible to register only the IP of
the normal host to the IP?

I want to remove 127.0.0.1 and 172.17.0.1 as shown in the log below.

How to only register 10.xxx.xxx.x to Ignite Cluster communication sockAddrs?

WARN  2018-01-31 03:34:15 [tcp-disco-msg-worker-#2%null%]
o.a.ignite.logger.java.JavaLogger.warning:278 - Received EVT_NODE_FAILED
event with warning [nodeInitiatedEvt=TcpDiscoveryNode
[id=9c9ee88b-d462-4ef2-9be7-edd21e01a7eb, addrs=[10.xxx.xxx.x, 127.0.0.1,
172.17.0.1],
sockAddrs=[ip-172-17-0-1.ap-northeast-2.compute.internal/172.17.0.1:47500,
/127.0.0.1:47500, /10.xxx.xxx.x:47500], discPort=47500, order=131,
intOrder=74, lastExchangeTime=1516101623966, loc=false,
ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false], msg=TcpCommunicationSpi
failed to establish connection to node [rmtNode=TcpDiscoveryNode
[id=65dcc3d9-3593-4b5e-9b80-c398abf9806f, addrs=[10.xxx.xxx.x, 127.0.0.1,
172.17.0.1],
sockAddrs=[ip-172-17-0-1.ap-northeast-2.compute.internal/172.17.0.1:47500,
/10.xxx.xxx.x:47500, /127.0.0.1:47500], discPort=47500, order=135,
intOrder=78, lastExchangeTime=1516101638624, loc=false,
ver=2.0.0#20170430-sha1:d4eef3c6, isClient=false], errs=class
o.a.i.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=65dcc3d9-3593-4b5e-9b80-c398abf9806f,
addrs=[ip-172-17-0-1.ap-northeast-2.compute.internal/172.17.0.1:47100,
ip-10-xxx-xxx-x.ap-northeast-2.compute.internal/10.xxx.xxx.x:47100,
/127.0.0.1:47100]], connectErrs=[class o.a.i.IgniteCheckedException: Failed
to connect to address:
ip-172-17-0-1.ap-northeast-2.compute.internal/172.17.0.1:47100, class
o.a.i.IgniteCheckedException: Failed to connect to address:
ip-10-xxx-xxx-x.ap-northeast-2.compute.internal/10.xxx.xxx.x:47100, class
o.a.i.IgniteCheckedException: Failed to connect to address:
/127.0.0.1:47100]]]

http://apache-ignite-users.70518.x6.nabble.com/How-to-correctly-shut-down-Ignite-Application-td12548.html

-Djava.net.preferIPv4Stack=true has not been applied yet. Or is this
related?

To summarize, I have two questions.

1. Is it possible to register only the IP of the normal host to the IP? (
exclude 127.0.0.1, 172.17.0.1 (docker container ip) )

2. -Djava.net.preferIPv4Stack=true has not been applied yet. Or is this
issue related?

Thanks.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/