[
https://issues.apache.org/jira/browse/IGNITE-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154475#comment-17154475
]
Taras Ledkov commented on IGNITE-9379:
--------------------------------------
[~alex_pl], the patch is OK with me.
But OOM is really bad case for application. We cannot be sure where OOM is
thrown: client thread / discovery thread etc.
So, I cannot obtain stable behavior of the grid on real OOM test case, e.g.
setup small heap size and load data set more than heap size. You could try to
check it for your patch.
> Ignite node hangs after OOM in a thread from thin client thread pool
> --------------------------------------------------------------------
>
> Key: IGNITE-9379
> URL: https://issues.apache.org/jira/browse/IGNITE-9379
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.6
> Reporter: Taras Ledkov
> Assignee: Aleksey Plekhanov
> Priority: Critical
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> OOM exception handler isn't set up for thin client thread pool.
> The issue is described in details at the [dev
> list|http://apache-ignite-evelopers.2346864.n4.nabble.com/Binary-Client-Protocol-client-hangs-in-case-of-OOM-on-server-td34224.html].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
