You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Greg Bowyer (JIRA)" <ji...@apache.org> on 2014/11/26 02:21:12 UTC
[jira] [Commented] (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=14225540#comment-14225540 ]
Greg Bowyer commented on SPARK-2445:
------------------------------------
It does not appear to be solved with SPARK-3555
{code}
gbowyer@compute-10-2-42-42 ~/spark-v1.1.0-rc4 $ cat RELEASE
Spark 1.1.2-SNAPSHOT (git revision 83a6b2c) built for Hadoop 2.3.0-cdh5.1.2
{code}
{code}
14/11/26 01:11:48 ERROR BlockManagerMasterActor: Got two different block manager registrations on 20140930-072242-1445331466-5050-8357-5
{code}
> 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