ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anton Vinogradov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6890) General way for handling Ignite failures (NodeInvalidator should be replaced with IgniteFailureProcessor)
Date Thu, 22 Feb 2018 11:42:00 GMT

     [ 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 (NodeInvalidator should be replaced
with IgniteFailureProcessor)  (was: General way for handling Ignite failures (NodeInvalidator
shuld be replaced with IgniteFailureProcessor))

> General way for handling Ignite failures (NodeInvalidator should be replaced with 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)

Mime
View raw message