[infinispan-issues] [JBoss JIRA] (ISPN-3443) Remove command may be ignored during state transfer

[RH Bugzilla Integration (JIRA)]

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

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

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

Distributed sync non-tx cache.
Situation:

1) A node is joining the cluster, requesting some segment
2) RemoveCommand is sent to backup owner with ignorePreviousValue=true
3) It looks up the entry and finds null
4) State transfer invokes the PutKeyValueCommand and sets the value for removed entry (updateKeys has not the key yet)
5) RemoveCommand adds its key to updateKeys set, but it does not remove the value as it is already null (in its context)

Result: the value is removed on primary but on backup this is still present
                
> Remove command may be ignored during state transfer
> ---------------------------------------------------
>
>                 Key: ISPN-3443
>                 URL: https://issues.jboss.org/browse/ISPN-3443
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Locking and Concurrency, State transfer
>    Affects Versions: 6.0.0.Alpha3
>            Reporter: Radim Vansa
>            Assignee: Dan Berindei
>
> Distributed sync non-tx cache.
> Situation:
> 1) A node is joining the cluster, requesting some segment
> 2) RemoveCommand is sent to backup owner with ignorePreviousValue=true
> 3) It looks up the entry and finds null
> 4) State transfer invokes the PutKeyValueCommand and sets the value for removed entry (updateKeys has not the key yet)
> 5) RemoveCommand adds its key to updateKeys set, but it does not remove the value as it is already null (in its context)
> Result: the value is removed on primary but on backup this is still present

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