You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Shuai Lin (JIRA)" <ji...@apache.org> on 2016/12/11 16:14:58 UTC
[jira] [Commented] (SPARK-18820) Driver may send "LaunchTask"
before executor receive "RegisteredExecutor"
[ https://issues.apache.org/jira/browse/SPARK-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15739970#comment-15739970 ]
Shuai Lin commented on SPARK-18820:
-----------------------------------
The driver first sends {{RegisteredExecutor}} message and then, if there is a task scheduled to run on this executor, sends the {{LaunchTask}} message, both through the same underlying netty channel. So I think the order is guaranteed, and the problem described would never happen.
> Driver may send "LaunchTask" before executor receive "RegisteredExecutor"
> -------------------------------------------------------------------------
>
> Key: SPARK-18820
> URL: https://issues.apache.org/jira/browse/SPARK-18820
> Project: Spark
> Issue Type: Bug
> Components: Scheduler
> Affects Versions: 1.6.3
> Environment: spark-1.6.3
> Reporter: jin xing
>
> CoarseGrainedSchedulerBackend will update executorDataMap after receiving "RegisterExecutor", thus task scheduler may assign tasks on to this executor;
> If LaunchTask arrives at CoarseGrainedExecutorBackend before RegisteredExecutor, it will result in NullPointerException and executor backend will exit;
> Is it a bug? If so can I make a pr? I think driver should send "LaunchTask" after "RegisteredExecutor" is already received.
--
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