[
https://issues.jboss.org/browse/ISPN-2566?page=com.atlassian.jira.plugin....
]
RH Bugzilla Integration commented on ISPN-2566:
-----------------------------------------------
Tomas Sykora <tsykora(a)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.
TopologyAwareConsistentHashFactory rebalance doesn't redistribute
data properly
-------------------------------------------------------------------------------
Key: ISPN-2566
URL:
https://issues.jboss.org/browse/ISPN-2566
Project: Infinispan
Issue Type: Bug
Components: Distributed Cache
Affects Versions: 5.2.0.Beta4
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 5.2.0.Beta6, 5.2.0.Final
Say we have a topology-aware cache with numOwners = 2 and two nodes: A(machine=m1) and
B(machine=m1). When node C(machine=m2) joins, it should own every key, either as a primary
or as a backup owner. This doesn't happen, node C owns just as many segments as nodes
A and B.
Example:
{noformat}
19:21:17,295 TRACE [org.infinispan.topology.ClusterTopologyManagerImpl] (undefined)
Updating cache topology topology for rebalance:
CacheTopology{id=3, currentCH=DefaultConsistentHash{numSegments=80, numOwners=2,
members=[node0/default(primary), node1/default(primary)],
owners={0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1,
8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1,
16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1,
24: 0 1, 25: 0 1, 26: 0 1, 27: 0 1, 28: 0 1, 29: 0 1, 30: 0 1, 31: 0 1,
32: 0 1, 33: 0 1, 34: 0 1, 35: 0 1, 36: 0 1, 37: 0 1, 38: 0 1, 39: 0 1,
40: 1 0, 41: 1 0, 42: 1 0, 43: 1 0, 44: 1 0, 45: 1 0, 46: 1 0, 47: 1 0,
48: 1 0, 49: 1 0, 50: 1 0, 51: 1 0, 52: 1 0, 53: 1 0, 54: 1 0, 55: 1 0,
56: 1 0, 57: 1 0, 58: 1 0, 59: 1 0, 60: 1 0, 61: 1 0, 62: 1 0, 63: 1 0,
64: 1 0, 65: 1 0, 66: 1 0, 67: 1 0, 68: 1 0, 69: 1 0, 70: 1 0, 71: 1 0,
72: 1 0, 73: 1 0, 74: 1 0, 75: 1 0, 76: 1 0, 77: 1 0, 78: 1 0, 79: 1 0},
pendingCH=DefaultConsistentHash{numSegments=80, numOwners=2,
members=[node0/default(primary), node1/default(primary), node2/default(secondary)],
owners={0: 0 1, 1: 0 1, 2: 0 1, 3: 0 1, 4: 0 1, 5: 0 1, 6: 0 1, 7: 0 1,
8: 0 1, 9: 0 1, 10: 0 1, 11: 0 1, 12: 0 1, 13: 0 1, 14: 0 1, 15: 0 1,
16: 0 1, 17: 0 1, 18: 0 1, 19: 0 1, 20: 0 1, 21: 0 1, 22: 0 1, 23: 0 1,
24: 0 1, 25: 0 1, 26: 0 1, 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 0, 41: 1 0, 42: 1 0, 43: 1 0, 44: 1 0, 45: 1 0, 46: 1 0, 47: 1 0,
48: 1 0, 49: 1 0, 50: 1 0, 51: 1 0, 52: 1 0, 53: 1 0, 54: 1 0, 55: 1 0,
56: 1 0, 57: 1 0, 58: 1 0, 59: 1 0, 60: 1 0, 61: 1 0, 62: 1 0, 63: 1 0,
64: 1 0, 65: 1 0, 66: 1 0, 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}}
{noformat}
--
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