Re: [infinispan-dev] DIST-SYNC, put(), a problem and a solution

Hey Dan, On 06/08/14 16:13, Dan Berindei wrote: I do believe the put-while-holding-the-lock issue *is* a critical issue; anyone banging a cluster of Infinispan nodes with more than 1 thread will run into lock timeouts, with or without transactions. The only workaround for now is to use total order, but at the cost of reduced performance. However, once a system starts hitting the lock timeout issues, performance drops to a crawl, way slower than TO, and work starts to pile up, which compounds the problem. I believe doing a sync RPC while holding the lock on a key is asking for trouble and is (IMO) an anti-pattern. Sorry if this has a negative impact on NBST, but should we not fix this because we don't want to risk a change to NBST ? I think this can be used for both cases; however, I think either Sanne's solution of using seqnos *per key* and updating in the order of seqnos or using Pedro's total order impl are probably better solutions. I'm not pretending these solutions are final (e.g. Sanne's solution needs more thought when multiple keys are involved), but we should at least acknowledge the issue exists, create a JIRA to prioritize it and then start discussing solutions. -- Bela Ban, JGroups lead (http://www.jgroups.org)