You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Kamlesh Joshi <Ka...@ril.com> on 2021/09/01 14:20:44 UTC
Client taking long time to connect to cluster
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 0.0.0.0:* LISTEN 38647/bwengine
tcp 0 0 0.0.0.0:10801 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 127.0.0.1:53 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."
Re: [External]Re: Client taking long time to connect to cluster
Posted by Gianluca Bonetti <gi...@gmail.com>.
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 gio 2 set 2021 alle ore 18:45 Ganguly Gundeboina <
gangaiah.yadav@gmail.com> ha scritto:
>
> 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.bonetti@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.Joshi@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 <yo...@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 <Ka...@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 <yo...@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 <Ka...@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."
>>>
>>
Re: [External]Re: Client taking long time to connect to cluster
Posted by Ganguly Gundeboina <ga...@gmail.com>.
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 <gi...@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.Joshi@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 <yo...@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 <Ka...@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 <yo...@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 <Ka...@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."
>>
>
Re: [External]Re: Client taking long time to connect to cluster
Posted by Gianluca Bonetti <gi...@gmail.com>.
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 <Ka...@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 <yo...@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 <Ka...@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 <yo...@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 <Ka...@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."
>
Re: [External]Re: Client taking long time to connect to cluster
Posted by Yohan Fernando <yo...@gmail.com>.
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 <Ka...@ril.com> wrote:
> Yohan, we have tried with JVM param as well, still its taking long time to
> connect.
>
>
>
> *Thanks and Regards,*
>
> *Kamlesh Joshi*
>
>
>
> *From:* Yohan Fernando <yo...@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 <Ka...@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 <yo...@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 <Ka...@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."
>
RE: [External]Re: Client taking long time to connect to cluster
Posted by Kamlesh Joshi <Ka...@ril.com>.
Yohan, we have tried with JVM param as well, still its taking long time to connect.
Thanks and Regards,
Kamlesh Joshi
From: Yohan Fernando <yo...@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 <Ka...@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 <yo...@gmail.com>>
Sent: 02 September 2021 14:44
To: user@ignite.apache.org<ma...@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 <Ka...@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."
Re: [External]Re: Client taking long time to connect to cluster
Posted by Yohan Fernando <yo...@gmail.com>.
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 <Ka...@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 <yo...@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 <Ka...@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."
>
RE: [External]Re: Client taking long time to connect to cluster
Posted by Kamlesh Joshi <Ka...@ril.com>.
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 <yo...@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 <Ka...@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."
Re: Client taking long time to connect to cluster
Posted by Yohan Fernando <yo...@gmail.com>.
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 <Ka...@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 0.0.0.0:*
> LISTEN 38647/bwengine
>
> tcp 0 0 0.0.0.0:10801 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 127.0.0.1:53
> 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."
>