You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2018/04/17 19:22:00 UTC

[jira] [Updated] (IGNITE-8304) Document failures handing in Ignite

     [ https://issues.apache.org/jira/browse/IGNITE-8304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denis Magda updated IGNITE-8304:
--------------------------------
    Description: 
IEP-14: https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling

The following failures will be treated as critical and can lead to an automatic node termination depending on configuration:
* System critical errors (e.g. OutOfMemoryError);
* Unintentional system worker termination (e.g. due to an unhandled exception);
* Cluster node segmentation.

In addition to that, the doc should cover how to utilize JVM pauses detector: https://issues.apache.org/jira/browse/IGNITE-6171

  was:
IEP-14: https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling

The following failures will be treated as critical and can lead to an automatic node termination depending on configuration:
* System critical errors (e.g. OutOfMemoryError);
* Unintentional system worker termination (e.g. due to an unhandled exception);
* Cluster node segmentation.

In addition to that the doc should cover how to utilize JVM pauses detector: https://issues.apache.org/jira/browse/IGNITE-6171


> Document failures handing in Ignite
> -----------------------------------
>
>                 Key: IGNITE-8304
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8304
>             Project: Ignite
>          Issue Type: Task
>          Components: documentation
>            Reporter: Denis Magda
>            Assignee: Andrey Gura
>            Priority: Major
>             Fix For: 2.5
>
>
> IEP-14: https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling
> The following failures will be treated as critical and can lead to an automatic node termination depending on configuration:
> * System critical errors (e.g. OutOfMemoryError);
> * Unintentional system worker termination (e.g. due to an unhandled exception);
> * Cluster node segmentation.
> In addition to that, the doc should cover how to utilize JVM pauses detector: https://issues.apache.org/jira/browse/IGNITE-6171



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)