Sanne,
this should work for you:
https://github.com/infinispan/infinispan/pull/4561
You're welcome :)
Tristan
On 19/09/16 15:24, Tristan Tarrant wrote:
> Yes, it means the client is not topology aware either.
>
> Tristan
>
> On 19/09/16 15:19, Sanne Grinovero wrote:
>> On 19 September 2016 at
Yes, it means the client is not topology aware either.
Tristan
On 19/09/16 15:19, Sanne Grinovero wrote:
> On 19 September 2016 at 13:52, Tristan Tarrant wrote:
>> Currently thee Java client always sets the client intelligence header to
>> 3 (topo + ch aware). We could add a configuration prope
On 19 September 2016 at 14:14, Gustavo Fernandes wrote:
> You can try to generate keys that hash to specific servers and use them.
> From the Hot Rod client you can
> get .getCacheTopologyInfo that gives you the segment ownership for the
> servers in the cluster, and to target
> a specific server
On 19 September 2016 at 13:52, Tristan Tarrant wrote:
> Currently thee Java client always sets the client intelligence header to
> 3 (topo + ch aware). We could add a configuration property so that you
> could specify 1 (basic).
> The alternative requires playing with the transport and playing wi
You can try to generate keys that hash to specific servers and use them.
>From the Hot Rod client you can
get .getCacheTopologyInfo that gives you the segment ownership for the
servers in the cluster, and to target
a specific server you'd craft a key that maps to a specific segment owned
by that se
Currently thee Java client always sets the client intelligence header to
3 (topo + ch aware). We could add a configuration property so that you
could specify 1 (basic).
The alternative requires playing with the transport and playing with the
"failed servers" but that is messy !
Tristan
On 19/
