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

Posted to issues@ignite.apache.org by "Anton Vinogradov (JIRA)" <ji...@apache.org> on 2018/02/22 11:42:00 UTC

[jira] [Updated] (IGNITE-6890) General way for handling Ignite failures (IgniteFailureProcessor

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

Anton Vinogradov updated IGNITE-6890:
-------------------------------------
    Summary: General way for handling Ignite failures (IgniteFailureProcessor   (was: General way for handling Ignite failures)

> General way for handling Ignite failures (IgniteFailureProcessor 
> -----------------------------------------------------------------
>
>                 Key: IGNITE-6890
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6890
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Anton Vinogradov
>            Assignee: Dmitriy Sorokin
>            Priority: Major
>              Labels: iep-14
>             Fix For: 2.5
>
>
> Ignite failures which should be handled are:
>  # Topology segmentation;
>  # Exchange worker stop;
>  # Errors currently covered by NodeInvalidator.
> Proper behavior should be selected according to result of calling IgniteFailureHandler instance, custom implementation of which can be provided in IgniteConfiguration. It can be node stop, restart or nothing.



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