[ 
https://issues.apache.org/jira/browse/IGNITE-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440427#comment-16440427
 ] 

ASF GitHub Bot commented on IGNITE-6892:
----------------------------------------

Github user alex-plekhanov closed the pull request at:

    https://github.com/apache/ignite/pull/3749


> OOM should be covered by failure handling
> -----------------------------------------
>
>                 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. We should consider uncaught or default exception handlers for other 
> treads: threads of system, public, etc. thread pools, all threads that are 
> instances of {{IgniteThread}}. 
> 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)

Reply via email to