[
https://issues.apache.org/jira/browse/IGNITE-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-6890:
--------------------------------
Description:
Ignite failures should be handled using common approach. IEP-14
(https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling)
introduces {{IgniteFailureHandler}} interface and describes all failures that
should be treated as critical.
was:
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.
See also IEP-14 "Ignite failures handling":
https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling
> 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 should be handled using common approach. IEP-14
> (https://cwiki.apache.org/confluence/display/IGNITE/IEP-14+Ignite+failures+handling)
> introduces {{IgniteFailureHandler}} interface and describes all failures
> that should be treated as critical.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
