[
https://issues.apache.org/jira/browse/IGNITE-24996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-24996:
---------------------------------------
Description: In many places in the project, when we catch an unexpected
exception which we don't know how to handle (or we can't handle it), we just
log it as an error or a warning. Instead, in many cases we need to notify the
failure processor because it could mean that some internal state is
inconsistent and we cannot proceed.
> Use failure handler instead of logging errors
> ---------------------------------------------
>
> Key: IGNITE-24996
> URL: https://issues.apache.org/jira/browse/IGNITE-24996
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In many places in the project, when we catch an unexpected exception which we
> don't know how to handle (or we can't handle it), we just log it as an error
> or a warning. Instead, in many cases we need to notify the failure processor
> because it could mean that some internal state is inconsistent and we cannot
> proceed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
