[infinispan-issues] [JBoss JIRA] (ISPN-2318) Reimplement a Topology-Aware Consistent Hash

[RH Bugzilla Integration (JIRA)]

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

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

Tomas Sykora <tsykora at redhat.com> made a comment on [bug 868832|https://bugzilla.redhat.com/show_bug.cgi?id=868832]

Hi Dan,

please, see the two latest TRACE logs for more information. In ER6/7 it was repaired server hinting for rack and site. Machine still seems to not working now.

When I was looking into logs I found these differencies:

for MACHINE (test is not passing):

14:22:16,074 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (OOB-76,null) Installing new cache topology CacheTopology{id=4, currentCH=DefaultConsistentHash{numSegments=1, numOwners=2, members=[node0/default(primary), node1/default(primary), node2/default(primary)], owners={0: 0 2}, pendingCH=null} on cache topology

for SITE (is ok, was fixed in ER6):

14:20:25,315 TRACE [org.infinispan.statetransfer.StateTransferManagerImpl] (OOB-76,null) Installing new cache topology CacheTopology{id=4, currentCH=DefaultConsistentHash{numSegments=80, numOwners=2, members=[node0/default(primary), node1/default(primary), node2/default(secondary)], owners={0: 0 2, 1: 0 2, 2: 0 2, 3: 0 2, 4: 0 2, 5: 0 2, 6: 0 2, 7: 0 2, 8: 0 2, 9: 0 2, 10: 0 2, 11: 0 2, 12: 0 2, 13: 0 2, 14: 0 2, 15: 0 2, 16: 0 2, 17: 0 2, 18: 0 2, 19: 0 2, 20: 0 2, 21: 0 2, 22: 0 2, 23: 0 2, 24: 0 2, 25: 0 2, 26: 0 2, 27: 2 0, 28: 2 0, 29: 2 0, 30: 2 0, 31: 2 0, 32: 2 0, 33: 2 0, 34: 2 0, 35: 2 0, 36: 2 0, 37: 2 0, 38: 2 0, 39: 2 0, 40: 1 2, 41: 1 2, 42: 1 2, 43: 1 2, 44: 1 2, 45: 1 2, 46: 1 2, 47: 1 2, 48: 1 2, 49: 1 2, 50: 1 2, 51: 1 2, 52: 1 2, 53: 1 2, 54: 1 2, 55: 1 2, 56: 1 2, 57: 1 2, 58: 1 2, 59: 1 2, 60: 1 2, 61: 1 2, 62: 1 2, 63: 1 2, 64: 1 2, 65: 1 2, 66: 1 2, 67: 2 1, 68: 2 1, 69: 2 1, 70: 2 1, 71: 2 1, 72: 2 1, 73: 2 1, 74: 2 1, 75: 2 1, 76: 2 1, 77: 2 1, 78: 2 1, 79: 2 1}, pendingCH=null} on cache topology

Can this be potencial problem?
Thank you very much for your investigation. If you need any other info, let me know.

Setting back ON_DEV for now despite of 2/3 was fixed and verified.
                
> Reimplement a Topology-Aware Consistent Hash
> --------------------------------------------
>
>                 Key: ISPN-2318
>                 URL: https://issues.jboss.org/browse/ISPN-2318
>             Project: Infinispan
>          Issue Type: Task
>          Components: Core API, Distributed Cache
>    Affects Versions: 5.2.0.Alpha3
>            Reporter: Erik Salter
>            Assignee: Dan Berindei
>            Priority: Blocker
>             Fix For: 5.2.0.Beta3
>
>
> Even with the advent of x-site replication, the TACH is useful to stripe key ownership across machines and/or racks for resiliency.  This feature should be refactored from the 5.1 impl.

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