ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6890) General way for handling Ignite failures (NodeInvalidator should be replaced with IgniteFailureProcessor)
Date Tue, 11 Dec 2018 13:03:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16717073#comment-16717073
] 

ASF GitHub Bot commented on IGNITE-6890:
----------------------------------------

Github user anton-vinogradov closed the pull request at:

    https://github.com/apache/ignite/pull/3558


> 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 {{FailureHandler}} interface and describes all failures that should be treated
as critical.



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

Mime
View raw message