You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2014/01/21 05:51:21 UTC

[jira] [Assigned] (TAJO-537) After TAJO-522, still OutOfMemoryError: unable to create new native thread

     [ https://issues.apache.org/jira/browse/TAJO-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi reassigned TAJO-537:
---------------------------------

    Assignee: Min Zhou

> After TAJO-522,  still OutOfMemoryError: unable to create new native thread
> ---------------------------------------------------------------------------
>
>                 Key: TAJO-537
>                 URL: https://issues.apache.org/jira/browse/TAJO-537
>             Project: Tajo
>          Issue Type: Bug
>          Components: distributed query plan
>    Affects Versions: 0.8-incubating
>            Reporter: Min Zhou
>            Assignee: Min Zhou
>            Priority: Critical
>             Fix For: 0.8-incubating
>
>         Attachments: TAJO-537-v2.patch, TAJO-537.patch
>
>
>  I ran a big query applied this patch, still OOM.  This is because if the quantity of different connections is large, Hyoungjun's patch won't help. Different connection create different thread pool.
> Actually, we can share the thread pool among all the clients.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)