[infinispan-issues] [JBoss JIRA] (ISPN-1830) L1: On topology changes we should propagate the key requestors information to the new owners

[Dan Berindei (JIRA)]

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

Dan Berindei commented on ISPN-1830:
------------------------------------

When a requestor leaves the cluster, we should probably remove it from any requestor list in order to free memory (and to not allow the requestor lists to grow indefinitely as nodes are restarted and re-join with a different address).
                
> L1: On topology changes we should propagate the key requestors information to the new owners
> --------------------------------------------------------------------------------------------
>
>                 Key: ISPN-1830
>                 URL: https://issues.jboss.org/browse/ISPN-1830
>             Project: Infinispan
>          Issue Type: Task
>          Components: Distributed Cache
>    Affects Versions: 5.1.0.FINAL
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 5.2.0.FINAL
>
>
> I think we are losing information about where a key needs to be invalidated when a node changes from owner to non-owner (e.g. because another node joined):
> * We lose the list of requestors stored on this node. Even if all ClusteredGetCommands reached all the current owners (which we are about to change with ISPN-825), once all the current owners leave the new owners will not know about this node's old requestors.
> * We don't add ourselves as a requestor for the key on the new owners when we invalidate the entry and move it to L1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira