You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ignite.apache.org by VeenaMithare <v....@cmcmarkets.com> on 2020/04/14 10:50:49 UTC

RE: Ignite Node failure - Node out of topology (SEGMENTED)

Hi Dmitry,

Would having a segmentation plugin help to resolve segmentation due to GC
pauses ?

Or is the best resolution for long GC pauses is to resolve it and get the GC
pauses to be within the failure detection timeout ?

regards,
Veena.




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

Re: Ignite Node failure - Node out of topology (SEGMENTED)

Posted by VeenaMithare <v....@cmcmarkets.com>.

Hi Evgenii,

Thank you for the reply and suggestion.

regards,
Veena.



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

Re: Ignite Node failure - Node out of topology (SEGMENTED)

Posted by Evgenii Zhuravlev <e....@gmail.com>.

Hi,

Segmentation plugin won't help with the issue itself. If you have a long GC
pause, it means that node is unresponsive for all this time. If you have GC
pause longer than 10 seconds, node will be dropped from the cluster(by
default). If you have long GC pauses, probably your load too big for your
configuration and it makes sense to increase heap or add more nodes to the
cluster.

Evgenii

вт, 14 апр. 2020 г. в 03:50, VeenaMithare <v....@cmcmarkets.com>:

> Hi Dmitry,
>
> Would having a segmentation plugin help to resolve segmentation due to GC
> pauses ?
>
> Or is the best resolution for long GC pauses is to resolve it and get the
> GC
> pauses to be within the failure detection timeout ?
>
> regards,
> Veena.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>