[infinispan-issues] [JBoss JIRA] Commented: (ISPN-977) KeyAffinityService has stale keys when topology changes

[Mircea Markus (JIRA)]

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

Mircea Markus commented on ISPN-977:
------------------------------------

Dan suggested another approach: transactions also get blocked during topology changes. That code might be used as well to determine when the new CH has been installed. AT that point just flush existing key and allow for new keys to be generated.

> KeyAffinityService has stale keys when topology changes
> -------------------------------------------------------
>
>                 Key: ISPN-977
>                 URL: https://issues.jboss.org/browse/ISPN-977
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 4.2.1.CR4
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>             Fix For: 4.2.2.FINAL, 5.0.0.CR2, 5.0.0.FINAL
>
>
> When the KAS is registered for single not cluster, when the cluster increases size, the old keys from KAS are not purged, resulting in an inconsistent key set. 
> Usable UT on the forums: http://community.jboss.org/message/592275#592275

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira