[infinispan-issues] [JBoss JIRA] (ISPN-1275) ConsistentHash implementation producing same hash id for two different cluster nodes
Galder Zamarreño (Updated) (JIRA)
jira-events at lists.jboss.org
Wed Oct 19 02:24:50 EDT 2011
[ https://issues.jboss.org/browse/ISPN-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Galder Zamarreño updated ISPN-1275:
-----------------------------------
Fix Version/s: 5.1.0.BETA3
(was: 5.1.0.BETA2)
> ConsistentHash implementation producing same hash id for two different cluster nodes
> ------------------------------------------------------------------------------------
>
> Key: ISPN-1275
> URL: https://issues.jboss.org/browse/ISPN-1275
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache
> Affects Versions: 5.0.0.FINAL
> Reporter: Galder Zamarreño
> Assignee: Manik Surtani
> Priority: Blocker
> Labels: consistent_hash
> Fix For: 5.1.0.BETA3, 5.1.0.FINAL
>
> Attachments: hashids.log
>
>
> While working on ISPN-1273, I've discovered that when virtual nodes are enabled, ConsistentHash.getHashIds(address) can return the same hash for two different cluster nodes. Example: with 500 virtual nodes, both NodeA-23181 and NodeB-39177 produce hash id *5289*. See attached log.
> Virtual nodes make the problem more apparent, however the problem exists regardless of vnodes being used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list