/commented by jason qian/ It is same result for "kill -9" as Ctrl-C.
But I find the reason and solution. There is an "org.apache.ignite.cache.CachePartialUpdateException" when the 1st node is killed. And there is an "org.apache.ignite.cache.CacheServerNotFoundException" when the last node is killed. I add try-catch in the test client to handle these 2 exceptions. Now the client will retry Put for "org.apache.ignite.cache.CachePartialUpdateException" and retry will succeed, and the client will error out for "org.apache.ignite.cache.CacheServerNotFoundException" (in fact, the client process always exit if all the data nodes are down). So after adding try-catch, the test client overcome the stop and hang issue. Thanks. ----- /This post is migrated from now discontinued Apache Ignite forum at http://apacheignite.readme.io/v1.0/discuss/ -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Client-hang-when-kill-1-node-in-2-node-data-grid-tp278p280.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
