You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:25:13 UTC
[jira] [Updated] (SPARK-16246) Too many
block-manager-slave-async-thread opened (TIMED_WAITING) for spark Kafka
streaming
[ https://issues.apache.org/jira/browse/SPARK-16246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-16246:
---------------------------------
Labels: bulk-closed (was: )
> Too many block-manager-slave-async-thread opened (TIMED_WAITING) for spark Kafka streaming
> ------------------------------------------------------------------------------------------
>
> Key: SPARK-16246
> URL: https://issues.apache.org/jira/browse/SPARK-16246
> Project: Spark
> Issue Type: Bug
> Components: DStreams, Spark Core
> Affects Versions: 1.6.1
> Reporter: Alex Jiang
> Priority: Major
> Labels: bulk-closed
>
> I don't know if our spark streaming issue is related to this (https://issues.apache.org/jira/browse/SPARK-15558).
> Basically we have one Kafka receiver on each executor, and it ran fine for a while. Then, the executor had a lot of waiting thread accumulated (Thread 1224: block-manager-slave-async-thread-pool-1083 (TIMED_WAITING)). And the executor kept open such new thread. Eventually, it reached the maximum number of the thread on that executor and Kafka receiver on that executor failed.
> Could someone please shed some light on this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org