Ignite 2.7.0 Off-heap evictions and replace()

Hi, We are using Apache Ignite 2.7.0 with the following setup 1. on-heap enabled 2. native persistence disabled 3. loading cache working with a database with write behind. 4. Random2LRU for off-heap evictions We are seeing that call to the replace() on a key returns false even though that was

Issue with serialization data security - 2.5.0

Hi, We are running into an issue with serialization security in Ignite 2.5.0 with whitelisting enabled. We start the cache inside an application in embedded mode. The cache is partitioned with read through/write behind enabled. I am getting the below exception while working with the cache.

cache closed or destroyed issue

Hi, We are facing an issue with Ignite cache where it throws an IllegalArgumentException with Cache closed or destroyed. I have two java applications that start the ignite cache in an embedded mode. The cache instances form a cache cluster with the help of zookeeper plugin for discovery. The

RE: OOM Issue with Eviction Event listener - Ignite 1.9.0

your Java process. On Mon, May 1, 2017 at 5:54 PM, Pradeep Badiger <pradeepbadi...@fico.com> wrote: > Hi, > > > > I am facing an OOM Exception when eviction policy is turned on. I have > attached an eclipse project that has two test programs. One is set > with ev

RE: Binary Marshalling issue

://apacheignite.gridgain.org/docs/binary-marshaller#binaryobject-cache-api On Fri, Dec 16, 2016 at 5:48 PM, Pradeep Badiger <pradeepbadi...@fico.com<mailto:pradeepbadi...@fico.com>> wrote: Hi Andrey, Thanks for your response. Is there a way I can disable it or reduce it? Do I need to use BinaryObj

RE: Binary Marshalling issue

issue Hi As I understand you have many short-lived Maps as values in cache. Yes, in your case, you can get a lot of garbage due to Map will be marshal\unmarshal along with each of its content at every cache entry access. On Fri, Dec 16, 2016 at 4:26 PM, Pradeep Badiger <pradeepbadi...@fico.

Binary Marshalling issue

Hi, I have an application which uses apache ignite cache in an embedded mode. On each GC cycle, I am seeing lot of memory getting retained. Cache has around 10K entries and each entry is an object containing a map of 500 entries. The key and value in the map within an object is string of less

RE: Evicted entry appears in Write-behind cache

that this entries cannot be evicted. If "get" invocation can not find value in cache, it will try to get value from CacheStore. On Fri, Oct 14, 2016 at 6:55 PM, Pradeep Badiger <pradeepbadi...@fico.com<mailto:pradeepbadi...@fico.com>> wrote: I have some log statements in

RE: Improve performance of ignite cluster

with the data to be processed as opposed to bring the data to a single processing node, etc -- but in all cases it's very application specific. Regards Andrey From: Pradeep Badiger <pradeepbadi...@fico.com<mailto:pradeepbadi...@fico.com>> Sent: Friday, Octo

RE: Improve performance of ignite cluster

@ignite.apache.org Subject: Re: Improve performance of ignite cluster Hi Pradeep, Why did you start several Ignite instances in one JVM? AFAIK it is recommended only for testing. In production it is recommended to start separate JVMs. On Fri, Oct 14, 2016 at 11:01 PM, Pradeep Badiger <pradeepbadi...@fico.

RE: Evicted entry appears in Write-behind cache

, which configured as "ReadThrough". On Thu, Oct 13, 2016 at 6:41 PM, Pradeep Badiger <pradeepbadi...@fico.com<mailto:pradeepbadi...@fico.com>> wrote: Hi Vladislav, Please see the below cache configuration. LruEvictionPolicy

RE: Evicted entry appears in Write-behind cache

sers.70518.x6.nabble.com/Cache-read-through-with-expiry-policy-td2521.html — Denis On Oct 11, 2016, at 8:55 AM, Pradeep Badiger <pradeepbadi...@fico.com<mailto:pradeepbadi...@fico.com>> wrote: Hi Denis, I did the get() on the evicted entry from the cache, it still returned me

RE: Evicted entry appears in Write-behind cache

from the write-behind store or from your underlying store. — Denis On Oct 8, 2016, at 1:00 PM, Pradeep Badiger <pradeepbadi...@fico.com<mailto:pradeepbadi...@fico.com>> wrote: Hi, I am trying to evaluate Apache Ignite and trying to explore eviction policy and write behind features.

Evicted entry appears in Write-behind cache

Hi, I am trying to evaluate Apache Ignite and trying to explore eviction policy and write behind features. I am seeing that whenever a cache is configured with eviction policy and write behind feature, the write behind cache always have all the changed entries including the ones that are

RE: performance issues

the benchmark using the client node the performance should be better rather with the configuration with less servers. — Denis On Jun 22, 2016, at 6:06 PM, Pradeep Badiger <pradeepbadi...@fico.com<mailto:pradeepbadi...@fico.com>> wrote: Hi Denis, Thanks for your response. I ran the be

RE: isolate/group ignite instances on same machine based on name

for convenience by application code. The isolation is achieved by using different configuration for communication and discovery SPIs as shown here https://apacheignite.readme.io/v1.6/docs/cluster-config#isolated-ignite-clusters-on-the-same-set-of-machin — Denis On Jun 19, 2016, at 2:21 AM, Pradeep Badiger

isolate/group ignite instances on same machine based on name

Hi, Is there a way to isolate or group multiple ignite instances on the same machine based on names rather than ports? Thanks, Pradeep V.B. This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If

performance issues

Hi, I am trying to run the yardstick ignite benchmark test on my local VM having 8 Cores and 16GB RAM. I could see that the performance of Optimistic PUT/GET is way low for a client-server mode than what I see when running within one single server (embedded mode). Also the performance degrades