1. Failure detection timeout doesn't affect the join process, so this is correct behavior. 2. I see your point, but setting joinTimeout looks like a good solution. Does it work for you? 3. Yes, that's OK, and in most cases servers and clients should have the same discovery configuration. TcpCommunicationSpi is used, but implicitly, with all defaults.
As for the instability over time, I would check if you don't have any memory issues. If the memory consumption grows, you will have longer GC pauses that can cause issues. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Client-fails-to-connect-joinTimeout-vs-networkTimeout-tp4419p4437.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
