Re: Node stopped automatically

[kvenkatramtreddy <kv...@gmail.com>]

Ignite related only that log,  
After that only  cache stopped exception in the log. 

Even we have enabled -DIGNITE_QUIET=false, but it is printing that much
only.





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Node stopped automatically

[Denis Mekhanikov <dm...@gmail.com>]

Venkat,

Please don't paste your logs into the body of your message, it makes them
look unreadable.
Use file attachment or provide a link instead.

Node on host 1 got segmented and killed according to the configured
segmentation policy.
It may happen due to a network problem or long GC pause.

Looks like you have persistence enabled and a single node in baseline
topology.
So, all data is actually stored on a single data node, and when it leaves
the grid, all partitions are marked as lost.
Refer to the documentation:
https://apacheignite.readme.io/docs/baseline-topology

You should add all nodes, that you want to store the data on, to the
baseline.
And when a node leaves topology forever, then you should drop it from the
baseline.

Denis

пн, 2 июл. 2018 г. в 12:15, kvenkatramtreddy <kv...@gmail.com>:

> Please could you provide some pointers, so that I can look deeper into the
> issue.
>
> 1) Does PageMemory cause any issues
>
> as per the metrics, one node is contains only 70  and other node is
> PageMemory [pages=390178]
>
> 2) Why whole cluster is going down, when one node is down
>
> 3) Can I restart the ignite programatically if this error occurs.
>
> Thanks & Regards,
> Venkat
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Node stopped automatically

[kvenkatramtreddy <kv...@gmail.com>]

Please could you provide some pointers, so that I can look deeper into the
issue. 

1) Does PageMemory cause any issues

as per the metrics, one node is contains only 70  and other node is
PageMemory [pages=390178]

2) Why whole cluster is going down, when one node is down

3) Can I restart the ignite programatically if this error occurs.

Thanks & Regards,
Venkat



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/