You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Brenden Matthews (JIRA)" <ji...@apache.org> on 2014/10/05 19:45:34 UTC
[jira] [Comment Edited] (SPARK-2445) MesosExecutorBackend crashes
in fine grained mode
[ https://issues.apache.org/jira/browse/SPARK-2445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159602#comment-14159602 ]
Brenden Matthews edited comment on SPARK-2445 at 10/5/14 5:45 PM:
------------------------------------------------------------------
[~drexin] can you confirm that SPARK-3535 resolves your issue?
was (Author: brenden):
[~drexin] can you confirm that https://issues.apache.org/jira/browse/SPARK-3535 resolves your issue?
> MesosExecutorBackend crashes in fine grained mode
> -------------------------------------------------
>
> Key: SPARK-2445
> URL: https://issues.apache.org/jira/browse/SPARK-2445
> Project: Spark
> Issue Type: Bug
> Components: Mesos
> Affects Versions: 1.0.0
> Reporter: Dario Rexin
>
> When multiple instances of the MesosExecutorBackend are running on the same slave, they will have the same executorId assigned (equal to the mesos slaveId), but will have a different port (which is randomly assigned). Because of this, it can not register a new BlockManager, because one is already registered with the same executorId, but a different BlockManagerId. More description and a fix can be found in this PR on GitHub:
> https://github.com/apache/spark/pull/1358
--
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