You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Subash Chaturanga <su...@gmail.com> on 2018/04/24 16:22:23 UTC

Ignite client to connect only to cache owners

Hi everyone,
Is there a way for a ignite client to connect only to the set of servers
who holds the cache or its backups. So that it will not requests from a
server which then has to talk to another node and return the values.

I know near cache is there, but that again increase allocated cache size to
the node and I wouldn’t be able to do a true partitioned cache.
-- 
/subash

Re: Ignite client to connect only to cache owners

Posted by "slava.koptilin" <sl...@gmail.com>.
Hello Subash,

The client node directly communicates with a primary node [1] from the
cluster (via TcpComminicationSpi [2]) in order to get a value from a cache.
There are no intermediate nodes. The same fact is correct for server nodes
as well.

[1] https://apacheignite.readme.io/docs/primary-and-backup-copies
[2] https://apacheignite.readme.io/docs/network-config#tcpcommunicationspi

Thanks!



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite client to connect only to cache owners

Posted by Eduard Shangareev <ed...@gmail.com>.
Hi, Subash,

By default, a cache is partitioned and partitions spread across the
cluster, so you can't avoid network activity.


On Tue, Apr 24, 2018 at 7:22 PM, Subash Chaturanga <su...@gmail.com>
wrote:

> Hi everyone,
> Is there a way for a ignite client to connect only to the set of servers
> who holds the cache or its backups. So that it will not requests from a
> server which then has to talk to another node and return the values.
>
> I know near cache is there, but that again increase allocated cache size
> to the node and I wouldn’t be able to do a true partitioned cache.
> --
> /subash
>