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

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,

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,

答复: 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:

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();

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

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

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