[
https://issues.apache.org/jira/browse/IGNITE-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-6892:
--------------------------------
Description:
{{java.lang.OutOfMemoryError}} should be handled accordingly to provided
failure handle.
There are at least 3 types of places where OOM can be catched:
1. Crtitical workers that listed in IEP-14. In this case we just handle
failures as {{CRITICAL _WORKER_TERMINATED}}.
2. Other threads. We should consider uncaught or default exception handlers for
such treads.
3. {{IgniteUtils.convertException()}} and
{{IgniteUtils.convertExceptionNoWrap}} methods that should invoke failure
handler in case of {{OutOfMemoryError}}.
Some memory should be reserved at node start to increase chances of OOM
handling.
was:
In case of any OOM node should be stopped anyway, what we can provide is user
callback, something like 'beforeNodeStop'.
Some memory should be reserved at node start to increase chances of OOM
handling.
> OOM should be covered by IgniteFailureProcessor
> -----------------------------------------------
>
> Key: IGNITE-6892
> URL: https://issues.apache.org/jira/browse/IGNITE-6892
> Project: Ignite
> Issue Type: Improvement
> Reporter: Anton Vinogradov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: iep-14
> Fix For: 2.5
>
>
> {{java.lang.OutOfMemoryError}} should be handled accordingly to provided
> failure handle.
> There are at least 3 types of places where OOM can be catched:
> 1. Crtitical workers that listed in IEP-14. In this case we just handle
> failures as {{CRITICAL _WORKER_TERMINATED}}.
> 2. Other threads. We should consider uncaught or default exception handlers
> for such treads.
> 3. {{IgniteUtils.convertException()}} and
> {{IgniteUtils.convertExceptionNoWrap}} methods that should invoke failure
> handler in case of {{OutOfMemoryError}}.
> Some memory should be reserved at node start to increase chances of OOM
> handling.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
