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

Erik Salter (JIRA) jira-events at lists.jboss.org
Mon Sep 17 11:32:35 EDT 2012


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

Erik Salter updated ISPN-2301:
------------------------------

        Summary: Grouped keys across caches do not have the same ownership information  (was: DefaultConsistentHash does not use group annotation.)
    Description: 
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.

  was:
Part of my design pattern is to use the Group API to group like-minded keys to the same segment.  The DefaultConsistentHash impl, in returning the primary owner of a key, uses the key's hash code instead of the Group annotation value.  According to TRACE logs, this results in remote LockControlCommand.

See the comments for ISPN-2291 for logs associated with such keys. (These keys use "edgeDeviceId=" as the group value.


    
> 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
>    Affects Versions: 5.2.0.Alpha3
>            Reporter: Erik Salter
>            Assignee: Mircea Markus
>
> 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


More information about the infinispan-issues mailing list