[
https://issues.apache.org/jira/browse/IGNITE-13055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169409#comment-17169409
]
Andrey N. Gura commented on IGNITE-13055:
-----------------------------------------
Such behavior is deliberate. It is failure handler responsibility to handle
such errors. We couldn't say anything about reason of such error and we also
couldn't predict cluster behavior after such errors. So the best approach is
triggering of failure handler.
> ExecutorServices must handle AssertionErrors and log uncaught exceptions
> ------------------------------------------------------------------------
>
> Key: IGNITE-13055
> URL: https://issues.apache.org/jira/browse/IGNITE-13055
> Project: Ignite
> Issue Type: Improvement
> Reporter: Maxim Muzafarov
> Priority: Major
>
> Currently, most of ExecuterServices (e.g. {{sysExecSvc}}) handles only
> OutOfMemoryException. Services must also handle AssertionErrors and log any
> uncaught exceptions.
> The most important list of executor services configured with OOM handler only:
> - execSvc
> - svcExecSvc
> - sysExecSvc
> - p2pExecSvc
> - restExecSvc
> - utilityCacheExecSvc
> - affExecSvc
> - qryExecSvc
> See the dev-list discussion for details.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
