Hi, As Alex said before, from the log you’ve provided it’s hard to say much but what’s in this message: =============== [09:06:26,657][WARNING][main][TcpDiscoverySpi] Node has not been connected to topology and will repeat join process. Check remote nodes logs for possible error messages. Note that large topology may require significant time to start. Increase 'TcpDiscoverySpi.networkTimeout' configuration property if getting this message on the starting nodes [networkTimeout=5000] ===============
Can you provide other log files and share more details about what specifically you’re doing? If the issue is reproducible in different environments, it would be helpful if you could share a reproducer project on GitHub. Thanks, Stan From: Lucky Sent: 6 марта 2018 г. 10:08 To: [email protected] Subject: Re:Re: Node can not join cluster Hi It's been over a few months. Are there any suggestions? Thanks. At 2017-12-15 23:35:49, "afedotov" <[email protected]> wrote: >Hi, > >From logs, I can see that the node was not able to connect to the cluster >due to a timeout issue. >It could be caused by GC or network issue. Please check the logs of other >nodes, especially of the coordinator >node fcc47ef7-f080-4f88-93f5-2bc221dd1fcf. > >Kind regards, >Alex > > > >-- >Sent from: http://apache-ignite-users.70518.x6.nabble.com/
