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

Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2026/02/09 17:00:00 UTC

[jira] [Updated] (IGNITE-21456) Use StopNodeFailureHandler instead of NoOpFailureHandler by default

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

Vyacheslav Koptilin updated IGNITE-21456:
-----------------------------------------
    Ignite Flags: Release Notes Required

> Use StopNodeFailureHandler instead of NoOpFailureHandler by default
> -------------------------------------------------------------------
>
>                 Key: IGNITE-21456
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21456
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vyacheslav Koptilin
>            Assignee: Vyacheslav Koptilin
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.2
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> The NoOpFailureHandler might be useful for testing and debugging purposes, however, it seems that the StopNodeFailureHandler is the right candidate for the default strategy for handling critical errors. It allows to stop nodes from a cluster that are encountered in an invalid state. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)