Query: Error in Ignite grid | CachePartialUpdateException

Hi, We often get following exception in our logs. Can someone help with root cause/reason and suggestion to fix it. Server is running on 2 nodes, replicated mode with cache having following configurations.

Query: Error in Ignite grid | CachePartialUpdateException

Hi, We often get following exception in our logs. Can someone help with root cause/reason and suggestion to fix it. Server is running on 2 nodes, replicated mode with cache having following configurations.

How off heap works

Hi, We are dealing with a large grid of 7 server name nodes where each node has multiple local caches. Data allocation rate at a few nodes is around 3gb/sec which will be moved to off heap cache (as gathered from young gen gc). However, heap consumption is very fast, one node even shows 50gb

Re: How off heap works

fheap consumes > some heap memory due to internal data structures' overhead. > > On Sun, Sep 11, 2016 at 8:59 PM, Anmol Rattan <anmolrat...@gmail.com> > wrote: > >> Hi, >> >> We are dealing with a large grid of 7 server name nodes where each node >> has mul

Re: Remote node gc pause

Created one for same. https://issues.apache.org/jira/browse/IGNITE-3898 Thanks & Regards Anmol Rattan +91 9538901262 On Fri, Sep 9, 2016 at 11:04 PM, vkulichenko <valentin.kuliche...@gmail.com> wrote: > Hi, > > I agree. Can you create a JIRA ticket for this? > &g

Re: Failed to get Item| Ignite queue

This may be because node of grid has > failed. > You can try to increase count of backup copies, look at the setBackups() > in CollectionConfiguration[1]. > > [1]: https://apacheignite.readme.io/v1.7/docs/queue-and-set# > collection-configuration > > On Wed, Sep 14, 2016 at 10:55

Re: OFFHEAP_VALUES ignoring max memory limit

Also, why there are two things eviction and expiration policy. We could have kept one class with exclusive property based on time (expiration) and eviction based on size. Regarding expiration, I have a specific requirement to keep 3 days worth cache data. However, that shall be rolled over weekend

Re: Segmentation policy.

I take that point. However, for custom scripts, is there a way to listen to segmentation event (please share name) and only from local node (local listener?) and in response to that event we could initialize beans or invoke our process. On Sep 10, 2016 3:24 AM, "vkulichenko"

Re: How to avoid the event lost in the continuous query

Hi Val, As you mentioned there is no loss of events, but there could be duplicates. For scenario, where strict time ordering is expected, getting results from listener first (not in client control) renders events coming from initial query as stale as listener responded earlier.e.g Cache has 77,78

Re: One failing node stalling the whole cluster

start process with ignite script. If prcoess has been started otherwise in a custom script, it does not support. Thanks & Regards Anmol Rattan +91 9538901262 On Fri, Sep 16, 2016 at 10:44 AM, yfernando <yohan.ferna...@tudor.com> wrote: > Hi Denis, > > We have been able to repro

Re: One failing node stalling the whole cluster

That would be topic for discussion on how off heap actually work. My understanding is to start with object creation will happen on heap (YG) and then moved to Old or Off heap. If allocation of object creation (I believe after that only you will associating them in a map (key.value cache), is