ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "javastuff.sam@gmail.com" <javastuff....@gmail.com>
Subject Re: Cluster hung after a node killed
Date Fri, 02 Dec 2016 19:51:35 GMT
Attaching 4 classes -
Node1.java - create empty cache node. 
Node2.java - seed cache with 100K <int,Str> dat.
Node3.java - take explicit lock on a key and wait for 15 seconds to unlock. 
Node4.java - fetch cached data.

Steps -
1. Run Node1, wait for empty node to boot up.
2. Run Node2, wait for completion message.
3. Run Node3, kill it when it prompts for "kill me...".
4. Run Node4 Topology snapshot on other node will show node joined, however
Node 4 will not able to complete with any fetch operations. Fetch from cache
hung.
5. Run another instance of Node2, it will not able to complete with any put
operation. Put to cache hung.

Node1.java
<http://apache-ignite-users.70518.x6.nabble.com/file/n9375/Node1.java>  
Node2.java
<http://apache-ignite-users.70518.x6.nabble.com/file/n9375/Node2.java>  
Node3.java
<http://apache-ignite-users.70518.x6.nabble.com/file/n9375/Node3.java>  
Node4.java
<http://apache-ignite-users.70518.x6.nabble.com/file/n9375/Node4.java>  



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9375.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message