Dominik,
This cache was already created in the cluster with Near Cace for all nodes.
Once created, this configuration can't be changed, so, it's needed to clean
persistence data or just destroy the cache and create it without Near Cache
in configuration. After this, you can dynamically add Near ca
Hi,
between first test with near cache configured in xml and configuring near
cache via java code i cleaned data.
But why should I clean data on server nodes when I add near cache only on
client nodes to gain performance?
Now I am testing ignite so I could do this, but it won't be acceptable when
r
Hi,
I see that you have persistence, did you clean the persistence directory
before changing configuration?
Evgenii
вт, 24 мар. 2020 г. в 02:33, Dominik Przybysz :
> Hi,
> I configured client node as you described in you email and heap usage on
> server nodes does not look as expected:
>
>
> +=
Hi,
I configured client node as you described in you email and heap usage on
server nodes does not look as expected:
+===+
| Node ID8(@), IP | CPUs | Heap Use
Hi,
exactly I want to have near cache only on client nodes. I will check your
advice with dynamic cache.
I have two server nodes which keep data and I want to get data from them
via my client nodes.
I am also curious what had happened with heap on server nodes.
pon., 23 mar 2020 o 23:13 Evgenii Z
Hi,
Near Cache configuration in xml creates near caches for all nodes,
including server nodes. As far as I understand, you want to have them on
client side only, right? If so, I'd recommend to create them dynamically:
https://www.gridgain.com/docs/latest/developers-guide/near-cache#creating-near-c
Hi,
I am using Ignite 2.7.6 and I have 2 server nodes with one partitioned
cache and configuration:
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
http://www.springframework.org/schema/beans
htt
