[infinispan-issues] [JBoss JIRA] (ISPN-2473) Forwarding for non-transactional write commands should be asynchronous

Dan Berindei (JIRA) jira-events at lists.jboss.org
Mon Nov 12 04:13:18 EST 2012


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

Dan Berindei reassigned ISPN-2473:
----------------------------------

    Assignee: Mircea Markus  (was: Dan Berindei)


Mircea, we've been talking about changing the locking scheme in non-tx caches in a way that would avoid these deadlocks. Please make this a dependency of the locking JIRA (and update the title/description if necessary).
                
> Forwarding for non-transactional write commands should be asynchronous
> ----------------------------------------------------------------------
>
>                 Key: ISPN-2473
>                 URL: https://issues.jboss.org/browse/ISPN-2473
>             Project: Infinispan
>          Issue Type: Sub-task
>          Components: State transfer
>    Affects Versions: 5.2.0.Beta3
>            Reporter: Dan Berindei
>            Assignee: Mircea Markus
>            Priority: Critical
>             Fix For: 5.2.0.CR1
>
>
> A write command keeps a lock on the originator while doing the RPC on the actual owners, so forwarding the command back to the originator synchronously leads to a deadlock.
> Keeping track of the real originator for forwarded commands could allow us to avoid the deadlock, but it would be too complicated. OTOH, non-tx caches don't guarantee consistency, so we could just do the forwarding asynchronously.

--
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


More information about the infinispan-issues mailing list