Hi, Evgenii Thank you for your reply.
The logs files are too big and same mostly, so collect the logs at the moment of connection. Because clients cannot connect to cluster any more and always show these error messages when we try to connect them again, I don't think it's the problem of that moment for long GC pause. At the same time, there are clients still can connect but after restarting these clients several times, they may cannot connect to cluster either. As time goes on, all clients cannot connect to cluster. If we restart one server node is still no use, clients cannot connect. When restart all server nodes and load data again, everything is OK. Do these circumstances indicate that it is not a network problem? There are several clients connected by VPN, is it possible to the client's restart regularly causing ignite socket communication to a certain degree of obstruction and becoming more and more serious as time goes by? Thanks -----邮件原件----- 发件人: ezhuravlev [mailto:[email protected]] 发送时间: 2018年1月30日 23:00 收件人: [email protected] 主题: Re: Re: Cannot connect the ignite server after running one or two days Hi, Looks like logs from the server is still not full. If you've checked them and you sure that you don't have any exceptions in it before witnessing this problem, then, I think that you could have some connection problems or a long GC pause. Do you have any network monitoring? Also, I would recommend checking GC logs at this moment(or share it with community) on all nodes. Also, Why did you set "queryThreadPoolSize" value="32" while you have only 24 CPUs for all 5 hosts? It's definitely will reduce performance due to a lot of context-switching. If everything okay with GC logs, it's possible to check TCP dumps, just to understand where the connection breaks off. Evgenii -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
