This content has been marked as final.
Show 4 replies
-
1. Re: How to aquire cluster-wide lock for non-transactional cache?
manik Mar 8, 2010 8:21 AM (in response to yelin66)You would need to catch your exception and retry unfortunately. If you were using transactions, though, you could use deadlock detection.
-
2. Re: How to aquire cluster-wide lock for non-transactional cache?
mircea.markus Mar 11, 2010 1:43 PM (in response to yelin66)incresing the1 of 1 people found this helpfulconcurrencyLevel would reduce the chance of lock overlaps, but as manik suggested I think retrying should be the solution for general case.
-
3. Re: How to aquire cluster-wide lock for non-transactional cache?
yelin66 Mar 11, 2010 2:41 PM (in response to mircea.markus)The default concurrencyLevel is 512, and my test has access from only two threads in two separate instances. I also tried to have different prefix for the keys I access from different threads. So basically there is no key collision. However, it happens quite frequently. Could you please suggest why and how to avoid it? -
4. Re: How to aquire cluster-wide lock for non-transactional cache?
mircea.markus Mar 11, 2010 3:57 PM (in response to yelin66)1 of 1 people found this helpfulyou won't be able to get rid of timeouts even if you disable lock striping; (but this would reduce the chance for this to happen, as you said).
beside disabling lock stipping, you can also increse replication timeout (try 20000 for example).