[
https://issues.apache.org/jira/browse/IGNITE-12198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934676#comment-16934676
]
Scott Feldstein commented on IGNITE-12198:
------------------------------------------
hi [~agura] & [~slava.koptilin], thanks for the notes. I don't see where
segmentation policy is mentioned in this doc ->
[https://apacheignite.readme.io/docs/critical-failures-handling]
Am I missing something? Is there a bug in the doc?
When i run this locally in my IDE with a simple failureHandler it see that it
is set properly in Ignite. The issue that necessitated this bug is something
that happened in our production env where our failureHandler wasn't called.
Tracing through the code we can clearly see that our failureHandler wasn't
called, instead it was the default handler.
> 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)
