Re: Ignite cache get operation not working, client application stucks at the initializaiton

Hi Evgenii, Could you please tell me how to check the type of field "ht" of model? I am currently running only one server node so I do not find any problem of version mismatch. Following are the Usecases: 1. Running same application parallely in client mode on same machine : everything works

Re: Ignite Client Heap out of Memory issue

Hi Andrey,Thanks for your replay. It still confused me for:1) for storm worker process, If it is  because of OOM and crashed. it should dump the heap. for I set  -XX:+HeapDumpOnOutOfMemoryError    but it didn't.  For storm worker, it behaves like a normal fatal error which make

[CVE-2018-1295]: Possible Execution of Arbitrary Code Within Deserialization Endpoints of Apache Ignite

CVE-2018-1295: Possible Execution of Arbitrary Code Within Deserialization Endpoints of Apache Ignite Severity: Important Vendor: The Apache Software Foundation Versions Affected: Apache Ignite 2.3 or earlier Impact: An attacker can execute arbitrary code on Ignite nodes in the case when

Where is the data stored in Durable Memory?

Hi Where is the data stored in Durable Memory? I want to find the data in hard disk. There is no description in the document. Thanks. Lucky.

Re: Webconsole on Hadoop/Spark cluster

Ganesh, Take a look for this docs: https://apacheignite-tools.readme.io/docs/getting-started On Mon, Apr 2, 2018 at 3:50 AM, ganesh wrote: > Hi > > I'm new bee to ignite. I have just installed Apache Ignite on Spark cluster > and tried running sample jobs. > > I found

Webconsole on Hadoop/Spark cluster

Hi I'm new bee to ignite. I have just installed Apache Ignite on Spark cluster and tried running sample jobs. I found about webconsole to monitor memory and metrics in ignite. Could you please you point me to steps to install webconsole on spark cluster? Appreciate you help Regards, Ganesh

Re:Re: Re:Re: Re:Issue about ignite-sql limit of table quantity

Thanks D. At 2018-04-01 23:07:25, "Dmitriy Setrakyan" wrote: Hi Fvyaba, In order to avoid memory overhead per table, you should create all tables as part of the same cache group: https://apacheignite.readme.io/docs/cache-groups D. On Mon, Mar 26, 2018 at 7:26

Re: Cache is too slow

There is always a way to improve the performance! Well, it depends on the size of your objects, machine, and network. You need to understand that it's a distributed system and it's obvious that it will not so fast as ConcurrentMap. Evgenii 2018-04-01 15:32 GMT+03:00 kvenkatramtreddy

Re: Fanout related query

On Tue, Mar 27, 2018 at 10:53 PM, Deepesh Malviya wrote: I notice that affinity solution is still going to update millions of items > but the updates are local instead of cluster-wide. Please let me know if my > interpretation is wrong. > Yes. > I see Ignite also support

Re: Re:Re: Re:Issue about ignite-sql limit of table quantity

Hi Fvyaba, In order to avoid memory overhead per table, you should create all tables as part of the same cache group: https://apacheignite.readme.io/docs/cache-groups D. On Mon, Mar 26, 2018 at 7:26 AM, aealexsandrov wrote: > Hi Fvyaba, > > I investigated your

Re: Build a cluster with auth

Hi, Ignite is adding basic authentication capability for thin clients in the upcoming 2.5 release - you will be able to provide user name and password to connect to the cluster: https://issues.apache.org/jira/browse/IGNITE-7436 You may already try it in the nightly builds:

Re: ClusterTopologyServerNotFoundException

Hi, Thank you very much. We are receiving this error only when one node was running. Exception is gone as soon other nodes are started and joined the cluster. I have attached the single node where we received the error. exception.log

Re: Cache is too slow

Hi, Thank you very much for your reply. I found that it is an issue with Webserver. I can see now Ignite cache is giving results are around 1-millisecond to 14 milliseconds with onheapEnabled and without onheapEnabled, results are around 3 milliseconds to 200 milliseconds. Are these expected

Re: Cache is too slow

Hi, Well, you're testing here not Ignite, but your JAX-RS services and Liberty server. Could you check it by removing the Ignite cache invocation at all? I'm pretty sure that you will get almost the same results without Ignite. If you want to check Ignite, you can use yardstick:

Re: ClusterTopologyServerNotFoundException

Hi, Looks like your cluster is unstable and part of the log you provided isn't enough to find the root cause of this. Could you provide logs from all nodes in the cluster for investigation? Thanks, Evgenii 2018-03-31 7:17 GMT+03:00 kvenkatramtreddy : > Hi, We have

Re: Ignite cache get operation not working, client application stucks at the initializaiton

Hi Priyanka, Are you sure that you have the same versions of classes on all nodes? What is the type of field "ht" in your model? *Could you please check that all nodes have the same versions of model classes?* *If you still have this problem, please share logs from client nodes too.* Regards,

Re: IgniteClient dead because of "java.lang.OutOfMemoryError: Java heap space Failed to process selector key"

Hey, Most possible it's just not enough heap memory for Ignite nodes or your application has the memory leak. How much java heap you've configured for nodes? Thanks, Evgenii 2018-03-31 6:54 GMT+03:00 RayEden : > I have 2 node for server and 3 node for client, I've got

Re: Distributed join does not work

Hey Vladyslav, Most possible that your data wasn't collocated. By default Ignite use joins only for collocated data and it's a preferable option. To read more about data collocation please check this doc: https://apacheignite.readme.io/docs/affinity-collocation Distributed joins without