Re: [External]Re: Client taking long time to connect to cluster

Hello there I would give it a try with -Djava.security.egd=file:/dev/urandom and -XX:+UseG1GC on both sides and see results. Another question, are both client and server running in the cloud, within the same datacentre? Or client and server run in different locations? Cheers Gianluca Il giorno

Streaming Patterns and Best Practices - featuring Apache Ignite

I just released a new video that includes using Ignite in a couple of design patterns: Streaming Patterns and Best Practices with Apache Pulsar for Enabling Machine Learning and Analytics I thought it might be of interest to the community. Devin G. Bost

Re: ignite dump

Any thoughts on this please? Note: This happens only on one node at a time after 2 to 3 days up time. Slowly builds up and ends up OOM. On multiple heap dumps detached connection only the 90% contributor. Current running version : 2.8.0 Thanks & Regards, Devakumar J On Wed, 1 Sep 2021, 12:04 DK

Re: [External]Re: Client taking long time to connect to cluster

Hi Gianluca, Thanks for your response. Below are jvm details for both server and client, *SERVER:* [tibusr@SERVERIP bin]$ ./java -version java version "1.8.0_251" Java(TM) SE Runtime Environment (build 1.8.0_251-b08) Java HotSpot(TM) 64-Bit Server VM (build 25.251-b08, mixed mode) export

Re: [External]Re: Client taking long time to connect to cluster

Hello I don't know if I can help you, but I'll give it a try, as I had problems for slow startup time in the past, and I solved them. Can you share a couple of information about JVM? Which JVM version are you using on the two different setups? Which JVM params are you using for them? Thank you C

Re: [External]Re: Client taking long time to connect to cluster

Have you tried turning up the logging level to see where it is spending the time? For example are you getting any system threads blocking etc? On Thu, Sep 2, 2021 at 11:01 AM Kamlesh Joshi wrote: > Yohan, we have tried with JVM param as well, still its taking long time to > connect. > > > > *Tha

RE: [External]Re: Client taking long time to connect to cluster

Yohan, we have tried with JVM param as well, still its taking long time to connect. Thanks and Regards, Kamlesh Joshi From: Yohan Fernando Sent: 02 September 2021 15:00 To: user@ignite.apache.org Subject: Re: [External]Re: Client taking long time to connect to cluster The e-mail below is from

Re: [External]Re: Client taking long time to connect to cluster

Seems like that VM arg is only read at startup time of the JVM according to this post, so setting it in code may not work https://stackoverflow.com/questions/9882357/how-to-set-java-net-preferipv4stack-true-at-runtime You might want to try it as a VM argument On Thu, Sep 2, 2021 at 10:22 AM Kaml

RE: [External]Re: Client taking long time to connect to cluster

Hi Yohan, We have already added this but not as a JVM param but via a code, like setting in system properties. Still the issue persists. Any other work around? Thanks and Regards, Kamlesh Joshi From: Yohan Fernando Sent: 02 September 2021 14:44 To: user@ignite.apache.org Subject: [External]Re

Re: Client taking long time to connect to cluster

We had a similar problem. Try adding -Djava.net.preferIPv4Stack=true to the VM parameters. On Wed, Sep 1, 2021 at 3:22 PM Kamlesh Joshi wrote: > Hi Igniters, > > > > We have upgraded OS version from Red Hat 6.10(Santiago) to 7.8(Maipo) in > Client server. Ignite cluster nodes’ OS are already on

apache ignite 2.10.0 heap starvation

After upgrading from 2.7.1 version to 2.10.0 version ignite nodes facing huge full GC operations after 24-36 hours after node start. We try to increase heap size but no luck, here is the start configuration for nodes; JVM_OPTS="$JVM_OPTS -Xms12g -Xmx12g -server -javaagent:/etc/prometheus/jmx_prom