[jira] [Updated] (IGNITE-17925) Ability to use configured FailureHandler for segmentation handling

["Aleksey Plekhanov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-17925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Plekhanov updated IGNITE-17925:
---------------------------------------
    Release Note: Added ability to use configured FailureHandler for segmentation handling

> Ability to use configured FailureHandler for segmentation handling
> ------------------------------------------------------------------
>
>                 Key: IGNITE-17925
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17925
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Ilya Shishkov
>            Assignee: Ilya Shishkov
>            Priority: Minor
>              Labels: ise
>             Fix For: 2.15
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Now, we have 3 possible ways to process segmentation by means of {{{}SegmentationPolicy{}}}:
>  # Stop segmented node - {{SegmentationPolicy#STOP}}
>  # Restart segmented node - {{SegmentationPolicy#RESTART_JVM}}
>  # Do nothing - {{SegmentationPolicy#NOOP}}
> Under the hood, behavior of segmentation handling (i.e. failure handling) is overridden [1, 2]. 
> For example, instead of using {{StopNodeOrHaltFailureHandler}} configured by default, default segmentation handling will use {{StopNodeFailureHandler}} which can hang during stop process.
> As a solution, we can add extra {{SegmentationPolicy#USE_FAILURE_HANDLER}} which will be used by default.
> Links:
>  # [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java#L3300]
>  # [https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/managers/discovery/GridDiscoveryManager.java#L2983]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)