Re: 答复: 答复: 答复: 答复: ignite Connection refused exception

[vkulichenko]

Kevin,

Actually, connections are not established frequently. If there is a lot of
communication between two nodes, they will create it once and then reuse. So
I'm not sure if it will cause degradation. In any case, this sounds like a
network issue. I would recommend to investigate this separately from Ignite,
using the network diagnostic tools like iperf and others.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-Connection-refused-exception-tp6412p6550.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

答复: 答复: 答复: 答复: ignite Connection refused exception

[Zhengqingzheng]

Hi Val,
After setting join timeout to 30s and socket timeout to 30s too. I can connect 
to the server.
If each connection takes so long time, it may cause performance issue. 
Do you have any suggestions on client to server connect?


Best regards,
Kevin

-邮件原件-
发件人: vkulichenko [mailto:valentin.kuliche...@gmail.com] 
发送时间: 2016年7月26日 6:45
收件人: user@ignite.apache.org
主题: Re: 答复: 答复: 答复: ignite Connection refused exception

Hi Kevin,

The exception itself is actually printed out only in DEBUG mode. It will always 
happen if you provide a range of addresses, but only some of them are 
available. So this is not an issue.

I noticed that it takes around a second to get 'Connection refused' from each 
address, so going through all of them can take some time. Can you try 
increasing the joinTimeout value to, for example, 30 seconds?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-Connection-refused-exception-tp6412p6523.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.