[
https://issues.apache.org/jira/browse/IGNITE-12198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934287#comment-16934287
]
Vyacheslav Koptilin commented on IGNITE-12198:
----------------------------------------------
Hi [~RohitJ23],
Yep, as Andrey mentioned above the implementation matches to the semantics of
{{SegmenationPolicy}}.
Please take a look here for detailed explanation:
-
[https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/plugin/segmentation/SegmentationPolicy.java]
- [https://apacheignite.readme.io/docs/critical-failures-handling]
If you want to trigger your own {{FailureHandler}} you just need to specify the
{{SegmentationPolicy.NOOP}} policy and listen for the
{{EventType#EVT_NODE_SEGMENTED}} event.
This allows implementing custom logic in order to handle segmentation.
> 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)
