Hello
On one hand I have a cluster of Ignite Server nodes target to store a
partitioned cache.
On the other hand I have some "legacy" compute code running in its own JVM on
the same nodes as Ignite nodes.
I would like to integrate in this compute JVM's an Ignite client joining the
cluster
> }
> );
>
> Here you find your neighbor via cluster API, then send a job executing a
> local query and returning all the data.
>
> Thanks,
> Stan
>
> From: Grégory Jevardat de Fombelle <mailto:gregory.jevar...@unige.ch>
> S
Hello
Is there any option to have a nearCache in Ignite that store unMarschalled
values instead of serialized ones. I ask this for performance reasons.
I noticed that for big cached objects, default Java unserialization is quite
expensive, like ~ 2 secs for a complex > 100MB object. So in the
Hello
We are facing this exception when multiple clients are trying to read a big
cached object using the standard value = cache.get(key).
The cached object is a big serialized object that can reach hundreds of MB in
size. The server node has 16GB of heap which should be fairly enough for
