ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey N. Gura (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-12198) GridDiscoveryManager uses hardcoded failure handler
Date Thu, 26 Sep 2019 11:20:00 GMT

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

Andrey N. Gura commented on IGNITE-12198:
-----------------------------------------

[~scottmf], you didn't missing anything. This aspect should be described in the docs.

[~Artem Budnikov] , could you please take a look? I can't find any information about segmentation
policies in the docs at all. Also "Critical Failures Handling" page should have note about
exceptional cases.

> GridDiscoveryManager uses hardcoded failure handler
> ---------------------------------------------------
>
>                 Key: IGNITE-12198
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12198
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.7.5
>            Reporter: Rohit Joshi
>            Priority: Major
>
> GridDiscoveryManager.onSegmentation() explicitly passes StopNodeFailureHandler to FailureProcessor
overriding the failureHandler provided in IgniteConfiguration.
> {code:java}
> case RESTART_JVM:
>     ctx.failure().process(new FailureContext(FailureType.SEGMENTATION, null), restartProcHnd);
>     break;
> case STOP:
>     ctx.failure().process(new FailureContext(FailureType.SEGMENTATION, null), stopNodeHnd);
>     break; {code}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message