tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Min Zhou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-537) After TAJO-522, still OutOfMemoryError: unable to create new native thread
Date Tue, 21 Jan 2014 06:17:19 GMT

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

Min Zhou commented on TAJO-537:
-------------------------------

Sure. Let's do it through another ticket. Actually, I still see over 300 threads in worker's
process if I run a big query. But the number will drop later. Seems it's due to the thread
pool is a cached pool. 

> 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)

Mime
View raw message