Re: Node is out of topology

[vdpyatkov <vl...@gmail.com>]

Hi,

What are you wan to check? Did not possible know frozen process or not into
themself.
Also you should set a alarm to this metric:

^-- CPU [cur=100%, avg=1.38%, *GC=1078.23%* ]

it means you node suffer from lot of garbage (which lead to SWT pause).

If you want to know when the node is segmented, you can subscribe to the
event[1] EVT_NODE_SEGMENTED

[1]: https://apacheignite.readme.io/docs/events#section-local-events



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Node-is-out-of-topology-tp13147p13310.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Node is out of topology

[vdpyatkov <vl...@gmail.com>]

Hi,

One way to re-join node to topology is stoping it and restart.

Node was not been join to cluster themself, because does not possible to
merge data between one cluster node (due to GC pause) and whole topology.
After the node left the cluster some of cache operation (put, remove) could
be and a simple return of node lets to inconsistent data.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Node-is-out-of-topology-tp13147p13372.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Node is out of topology

[vinshar <vi...@gmail.com>]

I think the question is that why node did not joined topology again after
garbage collection finished? Node can go out of topology for numerous
reasons but should it not join back when issue is resolved?  



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Node-is-out-of-topology-tp13147p13320.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.