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

Dmitriy Sorokin commented on IGNITE-6890:
-----------------------------------------

As was proposed by [~avinogradov] in discussion thread [Internal problems 
requiring graceful node shutdown, reboot, 
etc.|http://apache-ignite-developers.2346864.n4.nabble.com/Internal-problems-requiring-graceful-node-shutdown-reboot-etc-td24856.html],
 scheme with IgniteFailureHandler and IgniteFailureAction will be implemented:
{code}
interface IgniteFailureHandler { 
   IgniteFailureAction onFailure(IgniteFailureCause cause); 
} 

public enum IgniteFailureAction { 
    RESTART_JVM, 
    STOP, 
    NOOP; 
} 
{code}

Default implementation of IgniteFailureHandler will be implemented and enabled 
by default, and the ability of setting a custom user implementation in 
IgniteConfiguration will be added.

> Proper behavior on ExchangeWorker exits with error 
> ---------------------------------------------------
>
>                 Key: IGNITE-6890
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6890
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Anton Vinogradov
>            Assignee: Dmitriy Sorokin
>              Labels: iep-7
>             Fix For: 2.4
>
>
> Node should be stopped anyway, what we can provide is user callback, 
> something like beforeNodeStop'.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to