Val,
I have reproduced this with simple program -
1. Node 1 - run example ExampleNodeStartup
2. Node 2 - Run a program which create a transaction cache and add 100K
simple entries. <String, String>
cfg.setCacheMode(CacheMode.PARTITIONED);
cfg.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cfg.setMemoryMode(CacheMemoryMode.OFFHEAP_TIERED);
cfg.setSwapEnabled(false);
cfg.setBackups(0);
3. Node 3 - Run a program which takes a lock (cache.lock(key))
4. Kill Node 3 before it can unlock.
5. Node 4 - Run a program which tries to get cached data.
Node4 not able to join cluster, it is hung. In-fact complete cluster is hung
andy operation from Node2 also hung.
-Sam
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Cluster-hung-after-a-node-killed-tp8965p9337.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
