4:33 p.m.
Erik Salter created ISPN-2562:
---------------------------------
Summary: TopologyAwareConsistent hash not working as designed
Key: ISPN-2562
URL: https://issues.jboss.org/browse/ISPN-2562
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.2.0.Beta4
Reporter: Erik Salter
Assignee: Mircea Markus
The TACH does not appear to be functioning as designed. I specify two separate machines
(3 nodes each), but the backups are not distributed on the machines.
Here are TRACE logs (not of this system, unfortunately), but with the toString() of the
CHF used. Here are the specific implementations:
session-cluster (session, accountToSessionId, clientToSessionId): TACHF
erm-cluster (serviceGroup, qamAllocation, eigAllocation): SyncTACHF
https://dl.dropbox.com/u/50401510/10.30.12.159/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.160/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.163/server.log.gz
--
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
6:32 p.m.
[
https://issues.jboss.org/browse/ISPN-2562?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-2562:
------------------------------------
I need to investigate the SyncTACHF consistent hashes getting out of sync on the 3 caches
as well.
TopologyAwareConsistent hash not working as designed
----------------------------------------------------
Key: ISPN-2562
URL: https://issues.jboss.org/browse/ISPN-2562
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.2.0.Beta4
Reporter: Erik Salter
Assignee: Mircea Markus
The TACH does not appear to be functioning as designed. I specify two separate machines
(3 nodes each), but the backups are not distributed on the machines.
Here are TRACE logs (not of this system, unfortunately), but with the toString() of the
CHF used. Here are the specific implementations:
session-cluster (session, accountToSessionId, clientToSessionId): TACHF
erm-cluster (serviceGroup, qamAllocation, eigAllocation): SyncTACHF
https://dl.dropbox.com/u/50401510/10.30.12.159/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.160/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.163/server.log.gz
--
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
6:32 p.m.
[
https://issues.jboss.org/browse/ISPN-2562?page=com.atlassian.jira.plugin....
]
Dan Berindei reassigned ISPN-2562:
----------------------------------
Assignee: Dan Berindei (was: Mircea Markus)
TopologyAwareConsistent hash not working as designed
----------------------------------------------------
Key: ISPN-2562
URL: https://issues.jboss.org/browse/ISPN-2562
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.2.0.Beta4
Reporter: Erik Salter
Assignee: Dan Berindei
The TACH does not appear to be functioning as designed. I specify two separate machines
(3 nodes each), but the backups are not distributed on the machines.
Here are TRACE logs (not of this system, unfortunately), but with the toString() of the
CHF used. Here are the specific implementations:
session-cluster (session, accountToSessionId, clientToSessionId): TACHF
erm-cluster (serviceGroup, qamAllocation, eigAllocation): SyncTACHF
https://dl.dropbox.com/u/50401510/10.30.12.159/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.160/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.163/server.log.gz
--
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
6:34 p.m.
[
https://issues.jboss.org/browse/ISPN-2562?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-2562:
-------------------------------
Fix Version/s: 5.2.0.Final
TopologyAwareConsistent hash not working as designed
----------------------------------------------------
Key: ISPN-2562
URL: https://issues.jboss.org/browse/ISPN-2562
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.2.0.Beta4
Reporter: Erik Salter
Assignee: Dan Berindei
Fix For: 5.2.0.Final
The TACH does not appear to be functioning as designed. I specify two separate machines
(3 nodes each), but the backups are not distributed on the machines.
Here are TRACE logs (not of this system, unfortunately), but with the toString() of the
CHF used. Here are the specific implementations:
session-cluster (session, accountToSessionId, clientToSessionId): TACHF
erm-cluster (serviceGroup, qamAllocation, eigAllocation): SyncTACHF
https://dl.dropbox.com/u/50401510/10.30.12.159/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.160/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.163/server.log.gz
--
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
1:38 p.m.
[
https://issues.jboss.org/browse/ISPN-2562?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2562:
--------------------------------
Fix Version/s: 5.2.0.Beta6
TopologyAwareConsistent hash not working as designed
----------------------------------------------------
Key: ISPN-2562
URL: https://issues.jboss.org/browse/ISPN-2562
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.2.0.Beta4
Reporter: Erik Salter
Assignee: Dan Berindei
Fix For: 5.2.0.Final, 5.2.0.Beta6
The TACH does not appear to be functioning as designed. I specify two separate machines
(3 nodes each), but the backups are not distributed on the machines.
Here are TRACE logs (not of this system, unfortunately), but with the toString() of the
CHF used. Here are the specific implementations:
session-cluster (session, accountToSessionId, clientToSessionId): TACHF
erm-cluster (serviceGroup, qamAllocation, eigAllocation): SyncTACHF
https://dl.dropbox.com/u/50401510/10.30.12.159/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.160/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.163/server.log.gz
--
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
1:42 p.m.
[
https://issues.jboss.org/browse/ISPN-2562?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2562:
--------------------------------
Priority: Critical (was: Major)
TopologyAwareConsistent hash not working as designed
----------------------------------------------------
Key: ISPN-2562
URL: https://issues.jboss.org/browse/ISPN-2562
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.2.0.Beta4
Reporter: Erik Salter
Assignee: Dan Berindei
Priority: Critical
Fix For: 5.2.0.Final, 5.2.0.Beta6
The TACH does not appear to be functioning as designed. I specify two separate machines
(3 nodes each), but the backups are not distributed on the machines.
Here are TRACE logs (not of this system, unfortunately), but with the toString() of the
CHF used. Here are the specific implementations:
session-cluster (session, accountToSessionId, clientToSessionId): TACHF
erm-cluster (serviceGroup, qamAllocation, eigAllocation): SyncTACHF
https://dl.dropbox.com/u/50401510/10.30.12.159/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.160/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.163/server.log.gz
--
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
5:21 p.m.
[
https://issues.jboss.org/browse/ISPN-2562?page=com.atlassian.jira.plugin....
]
Dan Berindei resolved ISPN-2562.
--------------------------------
Fix Version/s: (was: 5.2.0.Final)
(was: 5.2.0.Beta6)
Resolution: Duplicate Issue
Erik, I've looked at the logs, but it seems to me all the nodes in erm-cluster and
session-cluster have the same transport configuration: clusterName='erm-cluster',
machineId='odrm1', rackId='rack1'.
Unfortunately we don't log the machineId/rackId when we log the address - I always
assumed that logging TopologyUUID.toString() would print those, but it seems it only
contains the site id. I did find these settings at the beginning of the log, when the
global configuration is logged.
I also couldn't find any sign of TopologyAwareSyncConsistentHashFactory being used.
This could be a problem in the configuration, can you check if you're configuring
TopologyAwareSyncConsistentHashFactory correctly?
Since I didn't find any new information in the logs, I'm closing this issue as a
duplicate of ISPN-2566. If you find other issues, particularly around
TopologyAwareSyncConsistentHashFactory, please open a new issue.
TopologyAwareConsistent hash not working as designed
----------------------------------------------------
Key: ISPN-2562
URL: https://issues.jboss.org/browse/ISPN-2562
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.2.0.Beta4
Reporter: Erik Salter
Assignee: Dan Berindei
Priority: Critical
The TACH does not appear to be functioning as designed. I specify two separate machines
(3 nodes each), but the backups are not distributed on the machines.
Here are TRACE logs (not of this system, unfortunately), but with the toString() of the
CHF used. Here are the specific implementations:
session-cluster (session, accountToSessionId, clientToSessionId): TACHF
erm-cluster (serviceGroup, qamAllocation, eigAllocation): SyncTACHF
https://dl.dropbox.com/u/50401510/10.30.12.159/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.160/server.log.gz
https://dl.dropbox.com/u/50401510/10.30.12.163/server.log.gz
--
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
4152
days inactive
4159
days old
infinispan-issues@lists.jboss.org
6 comments
3 participants
participants (3)
-
Dan Berindei (JIRA) -
Erik Salter (JIRA)
-
Mircea Markus (JIRA)