You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Chengxiang Li (JIRA)" <ji...@apache.org> on 2014/12/24 10:30:13 UTC
[jira] [Commented] (SPARK-4955) Executor does not get killed after
configured interval.
[ https://issues.apache.org/jira/browse/SPARK-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258138#comment-14258138 ]
Chengxiang Li commented on SPARK-4955:
--------------------------------------
I verified this feature with Hive on Spark, it works well in yarn-client mode, while failed to reduce to min executor number after idle timeout in yarn-cluster mode, here is the related appmaster log:
{noformat}
14/12/24 16:12:50 INFO cluster.YarnClusterSchedulerBackend: Requesting to kill executor(s) 2
14/12/24 16:12:50 WARN cluster.YarnClusterSchedulerBackend: Attempted to kill executors before the AM has registered!
14/12/24 16:12:50 WARN spark.ExecutorAllocationManager: Unable to reach the cluster manager to kill executor 2!
14/12/24 16:12:50 INFO cluster.YarnClusterSchedulerBackend: Requesting to kill executor(s) 1
14/12/24 16:12:50 WARN cluster.YarnClusterSchedulerBackend: Attempted to kill executors before the AM has registered!
14/12/24 16:12:50 WARN spark.ExecutorAllocationManager: Unable to reach the cluster manager to kill executor 1!
14/12/24 16:12:50 INFO cluster.YarnClusterSchedulerBackend: Requesting to kill executor(s) 4
14/12/24 16:12:50 WARN cluster.YarnClusterSchedulerBackend: Attempted to kill executors before the AM has registered!
14/12/24 16:12:50 WARN spark.ExecutorAllocationManager: Unable to reach the cluster manager to kill executor 4!
14/12/24 16:12:50 INFO cluster.YarnClusterSchedulerBackend: Requesting to kill executor(s) 3
14/12/24 16:12:50 WARN cluster.YarnClusterSchedulerBackend: Attempted to kill executors before the AM has registered!
14/12/24 16:12:50 WARN spark.ExecutorAllocationManager: Unable to reach the cluster manager to kill executor 3!
{noformat}
> Executor does not get killed after configured interval.
> -------------------------------------------------------
>
> Key: SPARK-4955
> URL: https://issues.apache.org/jira/browse/SPARK-4955
> Project: Spark
> Issue Type: Bug
> Components: YARN
> Affects Versions: 1.2.0
> Reporter: Chengxiang Li
>
> With executor dynamic scaling enabled, in yarn-cluster mode, after query finished and spark.dynamicAllocation.executorIdleTimeout interval, executor number is not reduced to configured min number.
--
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