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

RH Bugzilla Integration (JIRA) issues at jboss.org
Wed Aug 20 10:37:33 EDT 2014


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

RH Bugzilla Integration commented on ISPN-3530:
-----------------------------------------------

Tristan Tarrant <ttarrant at redhat.com> changed the Status of [bug 1029615|https://bugzilla.redhat.com/show_bug.cgi?id=1029615] from NEW to ASSIGNED

> 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
>      Security Level: Public(Everyone can see) 
>          Components: Remote Protocols
>    Affects Versions: 6.0.0.Alpha4
>            Reporter: Dan Berindei
>            Assignee: Galder Zamarreño
>              Labels: hotrod, hotrod-java-client
>             Fix For: 7.0.0.Alpha5
>
>
> 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 was sent by Atlassian JIRA
(v6.2.6#6264)



More information about the infinispan-issues mailing list