[infinispan-issues] [JBoss JIRA] (ISPN-2301) Grouped keys across caches do not have the same ownership information

[Dan Berindei (JIRA)]

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

Dan Berindei updated ISPN-2301:
-------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/1377


I created an alternative consistent hash factory that uses the JGroups
addresses to keep the CHs of different caches in sync. It's not the default,
so it needs to be configured explicitly with

In order to ignore the order of nodes in the members list, I made Address
implement Comparable - the JGroups Address was already Comparable.
                
> Grouped keys across caches do not have the same ownership information
> ---------------------------------------------------------------------
>
>                 Key: ISPN-2301
>                 URL: https://issues.jboss.org/browse/ISPN-2301
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core API, State transfer
>    Affects Versions: 5.2.0.Alpha3
>            Reporter: Erik Salter
>            Assignee: Dan Berindei
>            Priority: Blocker
>             Fix For: 5.2.0.CR1
>
>
> Part of my design pattern is to use the Group API to group like-minded keys across caches (on the same cache manager) to the same segment.  
> With the introduction of NBST, though, the same group key used across different caches results in different ownership information.  This is different behavior from 5.1.  
> (It looks like about a ~70% business logic degradation from 5.1 as well)
> See the comments for ISPN-2291 for logs associated with such keys. (These keys use "edgeDeviceId=" as the group 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