[infinispan-issues] [JBoss JIRA] (ISPN-3678) In replicated mode writeSkew check is executed only on coordinator

RH Bugzilla Integration (JIRA) jira-events at lists.jboss.org
Mon Nov 4 09:10:02 EST 2013


    [ https://issues.jboss.org/browse/ISPN-3678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846812#comment-12846812 ] 

RH Bugzilla Integration commented on ISPN-3678:
-----------------------------------------------

Radim Vansa <rvansa at redhat.com> made a comment on [bug 1026365|https://bugzilla.redhat.com/show_bug.cgi?id=1026365]

Write skew check should be always performed on primary owner - however, in replicated and invalidation modes this is executed only on the coordinator (and primary owner).

As a result, two conditional commands (e.g putIfAbsent) may both succeed to set the value.
                
> In replicated mode writeSkew check is executed only on coordinator
> ------------------------------------------------------------------
>
>                 Key: ISPN-3678
>                 URL: https://issues.jboss.org/browse/ISPN-3678
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 6.0.0.CR1
>            Reporter: Radim Vansa
>            Assignee: Pedro Ruivo
>            Priority: Critical
>
> Write skew check should be always performed on primary owner - however, in replicated and invalidation modes this is executed only on the coordinator (and primary owner). The bug is in ClusterDependentLogic.InvalidationLogic.
> As a result, two conditional commands (e.g putIfAbsent) may both succeed to set the value.

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