[infinispan-dev] Competing for cluster wide lock between state transfer and rehashing

Manik Surtani manik at jboss.org
Thu Mar 10 08:47:08 EST 2011


Yeah the processing lock in this case is on the Transport, which is shared by multiple caches.  The lock is used to maintain a coherent transaction log during state transfer or rehash.  Which means >1 cache cannot perform a rehash or state transfer at the same time.  We may be able to loosen this constraint, but this needs careful thought.  Create a JIRA for it?

In the meanwhile just make sure your state transfer or rehash timeouts take this into consideration.

On 10 Mar 2011, at 10:48, Galder Zamarreño wrote:

> Hi,
> 
> Re: https://issues.jboss.org/browse/JBPAPP-6052
> 
> I suspect here that the Hot Rod topology cache state transfer is competing with, most likely, the rehashing of distributed caches for the cluster wide distributed lock. 
> 
> Can someone (Manik?) remember why is this needed if clearly these two caches are unrelated? 
> 
> Cheers,
> --
> Galder Zamarreño
> Sr. Software Engineer
> Infinispan, JBoss Cache
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org






More information about the infinispan-dev mailing list