Comments on: Caching and Database Offloading – Best of both worlds with Terracotta Darwin Release http://www.ashishpaliwal.com/blog/2010/03/caching-and-database-offloading-best-of-both-worlds-with-terracotta-darwin-release/ From Programmer, For Programmers Mon, 09 Jan 2012 04:02:36 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: ashish http://www.ashishpaliwal.com/blog/2010/03/caching-and-database-offloading-best-of-both-worlds-with-terracotta-darwin-release/comment-page-1/#comment-25477 ashish Fri, 07 Jan 2011 06:24:00 +0000 http://www.ashishpaliwal.com/blog/?p=424#comment-25477 I saw the same question posted in Terracotta forum as well. Hope that was you. as it has been answered as well :) I saw the same question posted in Terracotta forum as well. Hope that was you. as it has been answered as well :)

]]> By: Grace http://www.ashishpaliwal.com/blog/2010/03/caching-and-database-offloading-best-of-both-worlds-with-terracotta-darwin-release/comment-page-1/#comment-25451 Grace Fri, 07 Jan 2011 00:53:11 +0000 http://www.ashishpaliwal.com/blog/?p=424#comment-25451 Hi Ashish, Thanks for the post. If I have two Terracotta clients running and Terracotta client#1 crashes and dies while processing line loadCache(), would my cluster ever become coherent again? In my test case, it seems that the cluster remains incoherent after client#1 dies. If that’s the case, it seems that client#2 would just be left hanging at the waitUntilClusterCoherent(). What would be a way around this indefinite wait? Ideally, I would also want client#2 to load whatever that client#1 didn’t complete loading. Thanks, Grace Hi Ashish,

Thanks for the post.
If I have two Terracotta clients running and Terracotta client#1 crashes and dies while processing line loadCache(), would my cluster ever become coherent again? In my test case, it seems that the cluster remains incoherent after client#1 dies.
If that’s the case, it seems that client#2 would just be left hanging at the waitUntilClusterCoherent(). What would be a way around this indefinite wait? Ideally, I would also want client#2 to load whatever that client#1 didn’t complete loading.

Thanks, Grace

]]>