[
https://issues.apache.org/jira/browse/IGNITE-6890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362581#comment-16362581
]
Anton Vinogradov commented on IGNITE-6890:
------------------------------------------
[~cyberdemon],
We should not map
case NOOP:
return NOOP;
Instead of doing this onSegmentation should call
IgniteFailureProcessor -> restartJvm or stopNode directly with correct reason
(IgniteFailureType)
> General way for handling Ignite failures
> ----------------------------------------
>
> Key: IGNITE-6890
> URL: https://issues.apache.org/jira/browse/IGNITE-6890
> Project: Ignite
> Issue Type: Improvement
> Reporter: Anton Vinogradov
> Assignee: Dmitriy Sorokin
> Priority: Major
> Labels: iep-7
> Fix For: 2.5
>
>
> Ignite failures which should be handled are:
> # Topology segmentation;
> # Exchange worker stop;
> # Persistence errors.
> Proper behavior should be selected according to result of calling
> IgniteFailureHandler instance, custom implementation of which can be provided
> in IgniteConfiguration. It can be node stop, restart or nothing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
