You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2020/08/11 13:18:00 UTC
[jira] [Commented] (SPARK-27510) Master fall into dead loop while
launching executor failed in Worker
[ https://issues.apache.org/jira/browse/SPARK-27510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17175560#comment-17175560 ]
Apache Spark commented on SPARK-27510:
--------------------------------------
User 'Ngone51' has created a pull request for this issue:
https://github.com/apache/spark/pull/29408
> Master fall into dead loop while launching executor failed in Worker
> --------------------------------------------------------------------
>
> Key: SPARK-27510
> URL: https://issues.apache.org/jira/browse/SPARK-27510
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.6.0, 2.0.0, 2.1.0, 2.2.0, 2.3.0, 2.4.0
> Reporter: wuyi
> Assignee: wuyi
> Priority: Major
> Fix For: 3.0.0
>
>
> In Standalone, while launching executor during ExecutorRunner.start() is always failed in Worker, Master will continue to launch new executor for the same Worker indefinitely.
> The issue is easy to reproduce by running a unit test with local-cluster mode and set a wrong spark.test.home(e.g. /tmp). Then, when running unit test, test would get stuck and we can see endless executor directories under /tmp/work/app/.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org