You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2017/03/29 08:54:41 UTC
[jira] [Commented] (SPARK-20135) spark thriftserver2: no job
running but containers not release on yarn
[ https://issues.apache.org/jira/browse/SPARK-20135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946748#comment-15946748 ]
Sean Owen commented on SPARK-20135:
-----------------------------------
There isn't enough detail here. It may be normal operation depending on your timeouts and settings. It isn't even clear you have enabled dynamic allocation. The mailing list is the right place to start with questions.
> spark thriftserver2: no job running but containers not release on yarn
> ----------------------------------------------------------------------
>
> Key: SPARK-20135
> URL: https://issues.apache.org/jira/browse/SPARK-20135
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.0.1
> Environment: spark 2.0.1 with hadoop 2.6.0
> Reporter: bruce xu
> Attachments: 0329-1.png, 0329-2.png, 0329-3.png
>
>
> i opened the executor dynamic allocation feature, however it doesn't work sometimes.
> i set the initial executor num 50, after job finished the cores and mem resource did not release.
> from the spark web UI, the active job/running task/stage num is 0 , but the executors page show cores 1276, active task 7288.
> from the yarn web UI, the thriftserver job's running containers is 639 without releasing.
> this may be a bug.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org