[
https://issues.apache.org/jira/browse/IGNITE-21460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17819625#comment-17819625
]
Kirill Tkalenko commented on IGNITE-21460:
------------------------------------------
Looks good.
> Add an ability to specify ignored failure types
> -----------------------------------------------
>
> Key: IGNITE-21460
> URL: https://issues.apache.org/jira/browse/IGNITE-21460
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vyacheslav Koptilin
> Assignee: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Motivation:
> It would be useful to introduce customized ignored failure types. The failure
> handler should be able to ignore some failures (just log a message) and not
> trigger node stopping. For example, long-running tasks in a critical worker
> might not be a reason for node stopping.
> Definition of done:
> The following two methods should be added to the FailureHandler interface:
> {code:java}
> /**
> * Sets failure types that must be ignored by failure handler.
> *
> * @param failureTypes Set of failure type that must be ignored.
> * @see FailureType
> */
> public void setIgnoredFailureTypes(Set<FailureType> failureTypes);
> /**
> * Returns unmodifiable set of ignored failure types.
> */
> public Set<FailureType> getIgnoredFailureTypes(); {code}
> Processing a failure from the list of ignored failure types should lead to
> logging a corresponding message and should not trigger node stopping.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
