ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dkarachentsev <dkarachent...@gridgain.com>
Subject Re: CacheAtomicityMode and CacheMode
Date Mon, 21 Aug 2017 17:40:45 GMT

1. In most cases that exception might be thrown if cache store cannot be
updated. Regularly even on unstable topology you won't get it, so the
easiest would be to do putAll() with failed keys, it should be finished

2. By default memory shared across all caches, so you may check space
consumed for all of them. To do that: 
consumed memory: MemoryMetrics.getPhysicalMemoryPages() * pageSize
memory and sick: MemoryMetrics.getTotalAllocatedPages() * pageSize
consumed disk: (MemeoryMetrics.getTotalAllocatedPages() -
MemoryMetrics.getPhysicalMemoryPages()) * pageSize

You cannot see metrics for specific cache, but you can apply MemoryPolicy
for specific cache and see metrics for that memory region.

3. Yes, in that case REPLICATED mode is most suitable.

4. By default client waits on put() unless primary nodes updated and backups
are set asynchronously. If you want to make sure that after put() all
changes applied for primary and backups, set

5. Try Ignite.cacheNames()


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CacheAtomicityMode-and-CacheMode-tp16313p16340.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message