Thanks Denis…
I understand that the example mentioned in the link is querying on the entity
named Person
CacheConfiguration cacheCfg = new CacheConfiguration<>();
...
cacheCfg.setName("mycache");
// Setting up query entity.
QueryEntity queryEntity = new QueryEntity();
> 2. By default all entries are saved off heap (not disk, heap outside the
Java heap to avoid GC problems), you can configure it to use heap or off
heap memory as you want.
This is the output from visor. I'm not completely sure what the difference
between off-heap and off-heap memory is here.
@DaveHarvey, I'll look at that tomorrow. Seems potentially complicated, but
if that's what has to happen we'll figure it out.
Interestingly, cutting the cluster to half as many nodes (by reducing the
number of backups) seems to have resolved the issue. Is there a guideline
for how large a
The keys are hashed so in theory they should be distributed relatively
evenly. I traced the logic to do the hashing once and it seemed ok, but it's
pretty complicated so I won't claim to know it that well. We use UUIDs and
it does seem to distribute pretty much evenly.
Are you sure all the nodes
Ignite related only that log,
After that only cache stopped exception in the log.
Even we have enabled -DIGNITE_QUIET=false, but it is printing that much
only.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
