[infinispan-issues] [JBoss JIRA] (ISPN-2552) Support concurrent updates for non-transactional caches

[Mircea Markus (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus updated ISPN-2552:
--------------------------------

    Priority: Blocker  (was: Major)

    
> Support concurrent updates for non-transactional caches 
> --------------------------------------------------------
>
>                 Key: ISPN-2552
>                 URL: https://issues.jboss.org/browse/ISPN-2552
>             Project: Infinispan
>          Issue Type: Feature Request
>    Affects Versions: 5.1.0.FINAL
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>            Priority: Blocker
>             Fix For: 5.2.0.CR1
>
>
> for non-transactional caches, when a key is updated, a local lock is acquired and also a lock on all the owning nodes as well. This is very inefficient for concurrent updates as it is very deadlock-prone.
> The following locking approach should solve this problem at the cost of an additional RPC: 
> - 'k' is written on node A, owners(k)={B,C}
> - A forwards the given command to B
> - B acquires a lock on 'k' then it forwards it to the remaining owners: C
> - C applies the change and returns to B (no lock acquisition is needed)
> - B applies the result as well, releases the lock and returns the result of the operation to A.
>   Note that even though this introduces an additional RPC (the forwarding), it behaves very well in conjunction with consistent-hash aware hotrod clients which connect directly to the lock owner.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira