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

[Manik Surtani (JIRA)]

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

Manik Surtani commented on ISPN-1275:
-------------------------------------

One way to minimise the scope of the problem, even with virtual nodes, is to increase the hash space (perhaps to Integer.MIN_VALUE ~ Integer.MAX_VALUE rather than 0 ~ 10000 or whatever we have right now).

But it still doesn't solve it completely.

> Virtual nodes 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
>             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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira