Hello!
1. I'm not sure, but perhaps this is due to necessity to track nodes with
near cache to keep it in sync.
2. I'm not sure there's the best way. Near cache is a cache, and
"cache" usually means "hot subset". The only way to be sure about complete
in-sync is to have a server node working on r
I have 3 questions:
1. Why do the server nodes use on heap storage when a client initializes a
dynamic near cache? We have never noticed any on-heap storage usage before
using a near cache on one of our clients.
Observe no caches initialized on server
Initialize a normal cache a
Hello!
"I always want a fully up to date copy of that cache" sounds like you need
a cache store actually.
Regards,
--
Ilya Kasnacheev
сб, 20 февр. 2021 г. в 04:05, tschauenberg :
> Hi,
>
> I have a use case where I want a fully copy of a replicated cache on a
> subset of my thick clients. In
Hi,
> it created a near cache on each server node
There are two Near Cache modes:
* Server Node Near Cache - configured once before cache start for all
server nodes
* Client Node Near Cache - configured dynamically on per-node basis
Please make sure to use the second mode, like explained in the
Hi,
I have a use case where I want a fully copy of a replicated cache on a
subset of my thick clients. In this example, I have an ETL thick client
that creates and updates a replicated cache in my server grid. I then have
a series of webserver thick clients that I always want a fully up to date
Hi,
I have a use case where I want a fully copy of a replicated cache on a
subset of my thick clients. In this example, I have an ETL thick client
that creates and updates a replicated cache in my server grid. I then have
a series of webserver thick clients that I always want a fully up to date
