[infinispan-issues] [JBoss JIRA] (ISPN-3530) The HotRod client should support a separate CH for each cache

[Mircea Markus (JIRA)]

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

Mircea Markus commented on ISPN-3530:
-------------------------------------

We should also check that the topology id is correctly computed for L2 replicated caches (no consistent hash)
                
> The HotRod client should support a separate CH for each cache
> -------------------------------------------------------------
>
>                 Key: ISPN-3530
>                 URL: https://issues.jboss.org/browse/ISPN-3530
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Remote protocols
>    Affects Versions: 6.0.0.Alpha4
>            Reporter: Dan Berindei
>            Assignee: Galder Zamarreño
>              Labels: hotrod, hotrod-java-client
>
> With asymmetric clusters, each cache can have its own consistent hash, so the primary owner of a key in one cache is not necessarily the owner in all the caches. Even with a symmetric cluster, the same client may be used to access both distributed and replicated caches, and those would certainly have a different CH.
> In order to send the operations to the correct owner, the HotRod client should use a different CH for each cache.

--
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