spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shixiong Zhu (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-11999) ThreadUtils.newDaemonCachedThreadPool(prefix, maxThreadNumber) has unexpected behavior
Date Thu, 26 Nov 2015 07:39:10 GMT

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

Shixiong Zhu resolved SPARK-11999.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0
                   1.5.3
                   1.4.2

> ThreadUtils.newDaemonCachedThreadPool(prefix, maxThreadNumber)  has unexpected behavior
> ---------------------------------------------------------------------------------------
>
>                 Key: SPARK-11999
>                 URL: https://issues.apache.org/jira/browse/SPARK-11999
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 1.4.1, 1.5.2, 1.6.0
>            Reporter: Shixiong Zhu
>            Assignee: Shixiong Zhu
>             Fix For: 1.4.2, 1.5.3, 1.6.0
>
>
> Currently, ThreadUtils.newDaemonCachedThreadPool(prefix, maxThreadNumber) will throw
RejectedExecutionException, if there are already `maxThreadNumber` busy threads and we submit
a new task. It's because `SynchronousQueue` cannot cache any task.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message