You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksey Plekhanov (Jira)" <ji...@apache.org> on 2020/07/09 11:32:00 UTC
[jira] [Commented] (IGNITE-9379) Ignite node hangs after OOM in a
thread from thin client thread pool
[ https://issues.apache.org/jira/browse/IGNITE-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154449#comment-17154449 ]
Aleksey Plekhanov commented on IGNITE-9379:
-------------------------------------------
[~tledkov-gridgain], can you please review the 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)