In the case of the test that I am executing, high contention caused by the test running as an Ignite client is causing not only the client but the whole cluster to become unresponsive upon subsequent destruction of the cache. The only way to get it to respond again seems to be to kill the client JVM - but that depends on identifying which client is causing the problem. Looking at the processor activity etc. doesn't seem to help because the cluster is not busy at this point - rather it is just hung along with everything else.
Because it's just a test that I'm running, I have the luxury of being able to kill the old clients and then test the cache for responsiveness by running a new client. As noted, this is a big improvement on v1.5 where the only way to recover was to restart the cluster. I'd be interested to know if v1.6 solved Ken's issue - which is probably a more common situation in production than mine. Regards, Colin. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Client-Blocks-On-Ignite-Server-Restart-tp4554p4646.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
