C++ Native Client

Hi, I want to use ignite from C++ & Java and have the following questions: 1. I want to use my own cross platform serialization (i.e. protobuf), that means that I'll put/get into ignite only byte arrays which are the product of protobuf serialization. What is the simplest way of havin

Re: ignite client memory issue

Hi, I assume this document for ignite server. In my case, I set ignite work at client mode. Now I increase the Max Heap Size and my application is running, I will monitor the memory usage. For my view, at client mode, ignite should not use too much memory. Thanks Shawn 发件人: Denis M

Re: ignite client memory issue

Also keep in mind that every Ignite node requires at least ~ 300 MB for its internal purposes. This capacity planning page might be useful as well for you: https://apacheignite.readme.io/docs/capacity-planning-bak — Denis > On Jan 21,

答复: ignite client memory issue

My heap max size is 768M. more than 500M are consumed by ignite. Your advice is quite reasonable. I will refactor my code. Thanks 发件人: Denis Magda [mailto:dma...@apache.org] 发送时间: 2017年1月22日 13:18 收件人: user@ignite.apache.org 主题: Re: ignite client memory issue Hi Shawn, What is

Re: Timed out waiting for message delivery receipt

Hi, The first thing I would check is that there are no long stop-the-world GC pauses in your cluster. Get to know this JVM and system tuning page: https://apacheignite.readme.io/docs/jvm-and-system-tuning — Denis > On Jan 21, 2017, at

Re: ignite client memory issue

Hi Shawn, What is the maximum size of the heap? I don’t think the cache configurations can be a reason of the OOM. As a side note, there is no reason to keep the configurations at all. Once a cache is started with a configuration you can either keep a single reference to it and reuse by multi

Re: Reusing Ignite-Marshaller leads to a Memory-Leak

Sorry, didn’t pay attention that the size of every object is 1 KB. Then I would suggest to share your test/heap dump to see what happens. — Denis > On Jan 21, 2017, at 9:10 PM, Denis Magda wrote: > > Hello Peter, > > This behavior is expected. Look, you serialize 2000 objects * 1000 KB which

Re: Reusing Ignite-Marshaller leads to a Memory-Leak

Hello Peter, This behavior is expected. Look, you serialize 2000 objects * 1000 KB which gives ~ 2 GB in total. After that you hold the references to these objects by putting them into an ordinary hash map. The objects will not be removed from the heap until the map keeps them. One the other s

答复: ignite client memory issue

I review the code, find a never released HashMap which store some cache configurations. private Map> cacheConfigurations = new HashMap<>(); I cache these configurations for performance consideration. I get ignite cache by calling: IgniteCache cache = IgniteManager.getIgnite().getOrCreateCache(conf

ignite client memory issue

Hi, My ignite client died many times recently because of OOM. Of course, I can increase the Max heap size. But I want to know why these memory are not released. This is part of analysis of Eclipse Memory Analyzer. My ignite client use Async cache API. please help. Class Name | Objects | Sh

Re: OOMs with Compute Grid

Hi Chris, Did you check the heap dump? What is consuming memory? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/OOMs-with-Compute-Grid-tp10169p10173.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reusing Ignite-Marshaller leads to a Memory-Leak

Hello Ignite-Community! I would like to use the Marshaller from Ignite for de-/serialising objects. I would like to re-use it, because it's very fast and I'm using Ignite anyway. I tried it with: //every thread gets the Marshaller via: GridKernalContext ctx = ((IgniteKernal) ignite).context(); M

Timed out waiting for message delivery receipt

I am trying to do POC with 4 Ignite server and 2 clients. But getting the below error on servers. {"@timestamp":"2017-01-21T16:51:27.168-05:00","@version":1,"message":"Timed out waiting for message delivery receipt (most probably, the reason is in long GC pauses on remote node; consider tuning GC

Re: Abandon of the non-throwing version of C++ client API

Hi Igor, My C++ experience is based only on error code methods. This is why I thought that exceptions based approach is unrelated to C++ at all. I do remember we discussed all the pros and cons of these ways before. Could you find that old discussion and share it here? I'm on a mobile now, not ea

OOMs with Compute Grid

Hello, We are doing a simple POC to see if Ignite will work for our needs. We built a small application that embeds Ignite and simulates what the real application does. The real application maintains a large in-memory HashMap (25GB) of RatePlans and then computes Rates with them The RatePlans ar