[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1275) ConsistentHash implementation producing same hash id for two different cluster nodes

[Dan Berindei (JIRA)]

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

Dan Berindei commented on ISPN-1275:
------------------------------------

It's not deterministic because some nodes might skip a view or a rebalance task, so they might not have the same old CH (see https://issues.jboss.org/browse/ISPN-1275?focusedCommentId=12617466&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12617466).

> 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.CR8
>            Reporter: Galder Zamarreño
>            Assignee: Manik Surtani
>            Priority: Blocker
>              Labels: consistent_hash
>             Fix For: 5.0.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira