Re: Reclaim memory from off-heap

Hi Stan, Thanks for the response. In our flow, we create, fill, destory and recreate cache in a for loop. I assume it would be still able to reuse what's already been allocated. Regards, Deepesh On Wed, Apr 18, 2018 at 12:07 AM, Stanislav Lukyanov wrote: > Hi, > > On

Re: Docker deployment with EXTERNAL_LIBS environment variable

I had the same problem (pretty common not having -i option) and fixed it. Need a review.https://issues.apache.org/jira/browse/IGNITE-8143 -- Roman On Tuesday, April 17, 2018, 7:15:25 p.m. GMT+9, Petr Ivanov wrote: Hi, Kseniya. I guess that something wrong with

Re: Slow invoke call

Thanks Val. I understand Array copy is heavy operation and probably lots of memory allocations too, however, my profiler showing complete logic of copy and append taking 50% of the total time taken by Invoke call. that's why the question, does invoke should take this much time or its the

RE: Efficiently determining if cache keys belong to the localservernode

Agree on the idempotent comments. Many of the requests are aggregative summarisations so there’ll need to be some additional tracking to detect double computation and missed computation in these cases. I understand that Ignite grids respond to requests during rebalancing operations where

Re: Reclaim memory from off-heap

Hi, On Tue, Apr 17, 2018 at 8:33 PM, Deepesh Malviya wrote: > Hi, > > I have read this post - http://apache-ignite-users. > 70518.x6.nabble.com/Cache-Destroy-Space-reclaim-td17208.html > > I have few questions > 1. Does this post is still true? > Yes. > 2. If cache destroy

Reclaim memory from off-heap

Hi, I have read this post - http://apache-ignite-users.70518.x6.nabble.com/Cache-Destroy-Space-reclaim-td17208.html I have few questions 1. Does this post is still true? 2. If cache destroy is called and is recreated, will it use same space or it will be new allocation on off-heap? 3. Is there

Re: How to upgrade Ignite 2.3 version to the latest version i.e. 2.4 version

Hi, Ignite does not support the rolling upgrade. To upgrade from 2.3 to 2.4 you could stop the whole cluster, update to 2.4 and restart the cluster. Please, look at page Cluster Activation and Baseline Topology Baseline Topology is the

How to upgrade Ignite 2.3 version to the latest version i.e. 2.4 version

Hi, We have 2.3 version server and client node.We want to upgrade to new version ,Is rolling upgrade support Ignite? or any other way is there to upgrade? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Off heap and JVM heap memory allocation

But please consider that you must have enough memory at least for running OS and it's services, also Ignite would warn you if you will try to use more than ~80% of RAM (70% in case if native persistence is enabled, and 90% if ignite is used in the pure in-memory mode). Best regards, Anton --

Re: Ignite spatial index behavior

Hi, Ignite provides envelope intersection, so it searches intersection of bounding box for a polygon and a certain point. Low 'hit-ratio' should not significantly affect to query performance. Could you please share a small piece of code or a project. 2018-04-15 10:42 GMT+03:00 olg.k...@gmail.com

RE: Efficiently determining if cache keys belong to the localservernode

> Is the failure mode of a node changing primality for a key during an affinity > co-located compute function handled by Ignite automatically for other > contexts? Are you asking whether or not affinityCall() would handle that? If so, then no, not really – once the job is sent to a node, it is

Re: Do we require to set MaxDirectMemorySize JVM parameter?

Hi Ankit, No, Ignite uses sun.misc.Unsafe for offheap memory. Direct memory may be used in DirectBuffers used for intercommunication. Usually defaults quite enough. Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Do we require to set MaxDirectMemorySize JVM parameter?

Hi All, Do we require to set MaxDirectMemorySize JVM parameter on IgniteServer to make use of OFFHEAP? For an example to make use of 8 GB off heap should I add MaxDirectMemorySize if yes then how much?

RE: Efficiently determining if cache keys belong to the local servernode

Hi Raymond, OK, I see, batching the requests makes sense. Have you looked at the ICacheAffinity interface? It provides a way to query Ignite about the key-to-node mappings, without dealing with partitions yourself. The call ignite.GetAffinity(“cache”).MapKeysToNodes(keys) is suitable to

Re: Docker deployment with EXTERNAL_LIBS environment variable

Hi, Kseniya. I guess that something wrong with wget in distribution (alpine-linux). I will need some testing to investigate further. > On 17 Apr 2018, at 13:02, Ksenia Vazhdaeva wrote: > > Hello, > > I am trying to deploy Apache Ignite 2.4.0 in docker using

Docker deployment with EXTERNAL_LIBS environment variable

Hello, I am trying to deploy Apache Ignite 2.4.0 in docker using external libs as described at https://apacheignite.readme.io/docs/docker-deployment /docker run -d --name ignite -v /storage/ignite/ignite-server-config.xml:/etc/ignite/ignite-server-config.xml \ -e