<div dir="ltr"><div>You can try to generate keys that hash to specific servers and use them. From the Hot Rod client you can <br>get .getCacheTopologyInfo that gives you the segment ownership for the servers in the cluster, and to target <br>a specific server you'd craft a key that maps to a specific segment owned by that server. I'd imagine the <br>implementation to be similar to [1] but for client-server mode.<br></div><br>[1] <a target="_blank" href="https://github.com/infinispan/infinispan/blob/master/core/src/test/java/org/infinispan/distribution/MagicKey.java">https://github.com/infinispan/<wbr>infinispan/blob/master/core/sr<wbr>c/test/java/org/infinispan/dis<wbr>tribution/MagicKey.java</a><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 19, 2016 at 1:52 PM, Tristan Tarrant <span dir="ltr"><<a target="_blank" href="mailto:ttarrant@redhat.com">ttarrant@redhat.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">Currently thee Java client always sets the client intelligence header to<br>
3 (topo + ch aware). We could add a configuration property so that you<br>
could specify 1 (basic).<br>
The alternative requires playing with the transport and playing with the<br>
"failed servers" but that is messy !<br>
<span><font color="#888888"><br>
Tristan<br>
</font></span><div><div><br>
On 19/09/16 13:39, Sanne Grinovero wrote:<br>
> Hi all,<br>
><br>
> I'm testing a concurrent update protocol based on Hot Rod client's<br>
> support for versioned entries.<br>
><br>
> I would love to be able to write a test having multiple client<br>
> endpoints, each connecting to a specific server. Of course HR's "smart<br>
> routing" prevents me from controlling this explicitly.. is there a way<br>
> to control it?<br>
><br>
> For example having servers {A, B} connected in cluster I'd like to<br>
> create two clients {A', B}', each one connected exclusively to one of<br>
> them and not aware of the other server node. (A <-> A', B <-> B').<br>
><br>
> Thanks,<br>
> Sanne<br>
> ______________________________<wbr>_________________<br>
> infinispan-dev mailing list<br>
> <a target="_blank" href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
> <a target="_blank" rel="noreferrer" href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailma<wbr>n/listinfo/infinispan-dev</a><br>
><br>
<br>
______________________________<wbr>_________________<br>
infinispan-dev mailing list<br>
<a target="_blank" href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>
<a target="_blank" rel="noreferrer" href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailma<wbr>n/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div></div>