Hello!
Since nobody is chiming in, my opinion is that:
1) Please don't try exceptions out of this handler!
2) I don't think you can switch it off, this is implemented as in other
places of JCache.
3) I think it still makes sense. Avoid blocking in continuous query handler.
As for your client-ser
Also some details on the cache config:
atomicityMode=TRANSACTIONAL
cacheMode = PARTITIONED
backups=1
.. the rest are default. Cache value types are binary objects.
So here's a simpler question, if my client node does a cache.put(key=String,
value=BinaryObject) 100 times on the same key, when are
Hi, I'm looking into an issue where we have an Ignite (2.6) client node doing
a CacheContinuousQuery on a cache full of binary objects, and eventually the
server node gets Out of Memory. Usually the server node is happy to run with
2-3 gig of Heap size, however when this client is running with a
Ca
