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 JVM_OPTS="$JVM_OPTS_SERVER -XX:+AlwaysPreTouch -XX:+UseG1GC -XX:+ScavengeBeforeFullGC -XX:+DisableExplicitGC -XX:+UnlockCommercialFeatures -XX:+PrintGCDetails -XX:+PrintAdaptiveSizePolicy -XX:+PrintGCTimeStamps -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=65 -XX:GCLogFileSize=10M -Xloggc:/backup/logs/gclog/gc.log -Djava.net.preferIPv4Stack=true -DIGNITE_LONG_OPERATIONS_DUMP_TIMEOUT=600000 -DIGNITE_THREAD_DUMP_ON_EXCHANGE_TIMEOUT=true" *CLIENT*: [sitibco@CLIENTIP bin]$ ./java -version java version "1.8.0_271" Java(TM) SE Runtime Environment (build 1.8.0_271-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode) java.heap.size.max=2048M java.heap.size.initial=512M java.extended.properties=-XX\:+UseConcMarkSweepGC -XX\:+CMSPermGenSweepingEnabled -XX\:+CMSClassUnloadingEnabled -XX\:PermSize\=512m -XX\:MaxPermSize\=512m -Djava.net.preferIPv4Stack=true Regards, Gangaiah On Thu, Sep 2, 2021 at 5:57 PM Gianluca Bonetti <gianluca.bone...@gmail.com> wrote: > 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 > Cheers > Gianluca > > Il giorno gio 2 set 2021 alle ore 12:01 Kamlesh Joshi < > kamlesh.jo...@ril.com> ha scritto: > >> Yohan, we have tried with JVM param as well, still its taking long time >> to connect. >> >> >> >> *Thanks and Regards,* >> >> *Kamlesh Joshi* >> >> >> >> *From:* Yohan Fernando <yohan.fernando.1...@gmail.com> >> *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 an external source. Please do not open >> attachments or click links from an unknown or suspicious origin. >> >> 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 Kamlesh Joshi <kamlesh.jo...@ril.com> >> wrote: >> >> 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 <yohan.fernando.1...@gmail.com> >> *Sent:* 02 September 2021 14:44 >> *To:* user@ignite.apache.org >> *Subject:* [External]Re: Client taking long time to connect to cluster >> >> >> >> The e-mail below is from an external source. Please do not open >> attachments or click links from an unknown or suspicious origin. >> >> 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 <kamlesh.jo...@ril.com> >> 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 7.8, we just >> upgraded client server OS. >> >> >> >> After upgrading client server, we are facing slow connections with >> cluster almost 5 mints. Sometimes it's not even able to connect to cluster >> from the client server, so had to retry multiple times. >> >> We have another client server with OS version 6.10 from which we are not >> facing such issue. >> >> >> >> *Is there any issue compatibility issue with Red Hat 7.8 version. We are >> using ignite 2.7.6 version.* >> >> >> >> *Please find netstat output below of upgraded client server:* >> >> >> >> Proto Recv-Q Send-Q Local Address Foreign Address >> State PID/Program name >> >> (Not all processes could be identified, non-owned process info >> >> will not be shown, you would have to be root to see it all.) >> >> tcp 0 0 0.0.0.0:47101 >> <https://protect2.fireeye.com/v1/url?k=f4f8b493-ab631c41-f4f93e6c-002590870bcc-cbcfd1ae6e65752e&q=1&e=9b8089c8-b380-40b8-bb36-28341ac14350&u=http%3A%2F%2F0.0.0.0%3A47101%2F> >> 0.0.0.0:* LISTEN 38647/bwengine >> >> tcp 0 0 0.0.0.0:10801 >> <https://protect2.fireeye.com/v1/url?k=5a0620fc-059d882e-5a07aa03-002590870bcc-921d5ddf6fec6227&q=1&e=9b8089c8-b380-40b8-bb36-28341ac14350&u=http%3A%2F%2F0.0.0.0%3A10801%2F> >> 0.0.0.0:* LISTEN 38647/bwengine >> >> *tcp 6674800 0 ClientIP:49917 ServerIP:47500 >> ESTABLISHED 38647/bwengine* >> >> udp 0 0 127.0.0.1:49634 >> <https://protect2.fireeye.com/v1/url?k=639f5349-3c04fb9b-639ed9b6-002590870bcc-75bf9510e355eff1&q=1&e=9b8089c8-b380-40b8-bb36-28341ac14350&u=http%3A%2F%2F127.0.0.1%3A49634%2F> >> 127.0.0.1:53 >> <https://protect2.fireeye.com/v1/url?k=048f0efb-5b14a629-048e8404-002590870bcc-58dca837aa1e0fe7&q=1&e=9b8089c8-b380-40b8-bb36-28341ac14350&u=http%3A%2F%2F127.0.0.1%3A53%2F> >> ESTABLISHED 38647/bwengine >> >> unix 2 [ ] STREAM CONNECTED 142186514 38647/bwengine >> >> unix 3 [ ] STREAM CONNECTED 142148803 38647/bwengine >> >> unix 2 [ ] STREAM CONNECTED 142053176 38647/bwengine >> >> unix 3 [ ] STREAM CONNECTED 142112733 38647/bwengine >> >> unix 3 [ ] STREAM CONNECTED 142148802 38647/bwengine >> >> unix 3 [ ] STREAM CONNECTED 142112732 38647/bwengine >> >> >> >> Any pointers on this would be helpful. >> >> >> >> *Thanks and Regards,* >> >> *Kamlesh Joshi* >> >> >> >> >> "*Confidentiality Warning*: This message and any attachments are >> intended only for the use of the intended recipient(s), are confidential >> and may be privileged. If you are not the intended recipient, you are >> hereby notified that any review, re-transmission, conversion to hard copy, >> copying, circulation or other use of this message and any attachments is >> strictly prohibited. If you are not the intended recipient, please notify >> the sender immediately by return email and delete this message and any >> attachments from your system. >> >> *Virus Warning:* Although the company has taken reasonable precautions >> to ensure no viruses are present in this email. The company cannot accept >> responsibility for any loss or damage arising from the use of this email or >> attachment." >> >> >> "*Confidentiality Warning*: This message and any attachments are >> intended only for the use of the intended recipient(s), are confidential >> and may be privileged. If you are not the intended recipient, you are >> hereby notified that any review, re-transmission, conversion to hard copy, >> copying, circulation or other use of this message and any attachments is >> strictly prohibited. If you are not the intended recipient, please notify >> the sender immediately by return email and delete this message and any >> attachments from your system. >> >> *Virus Warning:* Although the company has taken reasonable precautions >> to ensure no viruses are present in this email. The company cannot accept >> responsibility for any loss or damage arising from the use of this email or >> attachment." >> >> >> "*Confidentiality Warning*: This message and any attachments are >> intended only for the use of the intended recipient(s), are confidential >> and may be privileged. If you are not the intended recipient, you are >> hereby notified that any review, re-transmission, conversion to hard copy, >> copying, circulation or other use of this message and any attachments is >> strictly prohibited. If you are not the intended recipient, please notify >> the sender immediately by return email and delete this message and any >> attachments from your system. >> >> *Virus Warning:* Although the company has taken reasonable precautions >> to ensure no viruses are present in this email. The company cannot accept >> responsibility for any loss or damage arising from the use of this email or >> attachment." >> >
