[
https://issues.apache.org/jira/browse/IGNITE-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154482#comment-17154482
]
Aleksey Plekhanov commented on IGNITE-9379:
-------------------------------------------
[~tledkov-gridgain], thanks for the review!
I believe most of the OOM cases are covered by IGNITE-6892. But additionally, I
will try to reproduce case from dev list locally (without unit test), if
everything is ok, I will merge the patch (after TC bot visa).
> 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)
