Hello!

Do you also have logs from other server nodes?

Here, I don't see anything particularly suspicious. Maybe there indeed were
some short-term network problems?

Regards,
-- 
Ilya Kasnacheev


ср, 6 янв. 2021 г. в 15:04, BEELA GAYATRI <beela.gaya...@tcs.com>:

> Dear Team,
>
>
>
> We are running 16  Ignite nodes, few nodes are getting down with  below
> error . Please let us know what could be possible reasons and solution  if
> node is segmented and getting down.
>
> *Error:*
>
> *Node is out of topology (probably, due to short-time network problems).*
>
> *[23:16:27,554][WARNING][disco-event-worker-#40%MATCHERWORKER%][GridDiscoveryManager]
> Local node SEGMENTED: TcpDiscoveryNode
> [id=ad4f2ad9-7f42-4863-84e4-03b95c6a9d9d, addrs=[XX.XX.XXX.IP8, 127.0.0.1],
> sockAddrs=[/127.0.0.1:47500 <http://127.0.0.1:47500>,
> SERVER8/XX.XX.XXX.IP8:47500], discPort=47500, order=8, intOrder=8,
> lastExchangeTime=1609868787545, loc=true, ver=2.7.0#20181201-sha1:256ae401,
> isClient=false]*
>
>
>
> Below are he jvm args we are providing to the nodes
>
> JVMARGS="-Xms3G -Xmx3G -Xss5M -XX:-UseGCOverheadLimit
>
> -XX:+AlwaysPreTouch
>
> -XX:+UseG1GC
>
> -XX:+ScavengeBeforeFullGC
>
> -XX:+DisableExplicitGC
>
> -XX:+PrintGCDetails
>
> -XX:MaxGCPauseMillis=200
>
> -Xloggc:/path/to/logs/GClog.txt
>
> Djava.net.preferIPv4Stack=true  -Dserver --add-exports
> java.base/jdk.internal.misc=ALL-UNNAMED --add-exports 
> java.base/sun.nio.ch=ALL-UNNAMED
> --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED
> --add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED"
>
>
>
> PFA the log attached
>
>
>
>
>
> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
>
>
>
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>

Reply via email to