Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 27 Sep 2017 13:53:00 +0000 (UTC)
From: "Stavros Kontopoulos (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.13105386.1506510755000.215140.1506520380398@Atlassian.JIRA>
In-Reply-To: <JIRA.13105386.1506510755000@Atlassian.JIRA>
References: <JIRA.13105386.1506510755000@Atlassian.JIRA> <JIRA.13105386.1506510755269@jira-lw-us.apache.org>
Subject: [jira] [Updated] (SPARK-22145) Issues with driver re-starting on
 mesos (supervise)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 27 Sep 2017 13:53:05 -0000


     [ https://issues.apache.org/jira/browse/SPARK-22145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stavros Kontopoulos updated SPARK-22145:
----------------------------------------
    Description: 
There are two issues with driver re-starting on mesos using the supervise flag:
- We need to add spark.mesos.driver.frameworkId to the reloaded properties for checkpointing, otherwise the new frameworkId propagated by the dispatcher will be overwritten by the checkpointed data.
- Unique task ids are not used by the dispatcher:
https://issues.apache.org/jira/browse/MESOS-4737
https://issues.apache.org/jira/browse/MESOS-3070
This issue is the same in principle as the case with standalone mode where the master needs to re-launch drivers with a new appId (driverId) to deal with net partitions, but it affects mesos not spark, since we use 
different driver ids anyway when we re-launch a driver.


  was:
There are two issues with driver re-starting on mesos using the supervise flag:
- We need to add spark.mesos.driver.frameworkId to the reloaded properties for checkpointing, otherwise the new frameworkId propagated by the dispatcher will be overwritten by the checkpointed data.
- Unique task ids are not used by the dispatcher:
https://issues.apache.org/jira/browse/MESOS-4737
https://issues.apache.org/jira/browse/MESOS-3070
This issue is the same as the case with standalone mode where the master re-launches drivers with a new appId (driverId)


> Issues with driver re-starting on mesos (supervise)
> ---------------------------------------------------
>
>                 Key: SPARK-22145
>                 URL: https://issues.apache.org/jira/browse/SPARK-22145
>             Project: Spark
>          Issue Type: Bug
>          Components: Mesos
>    Affects Versions: 2.3.0
>            Reporter: Stavros Kontopoulos
>
> There are two issues with driver re-starting on mesos using the supervise flag:
> - We need to add spark.mesos.driver.frameworkId to the reloaded properties for checkpointing, otherwise the new frameworkId propagated by the dispatcher will be overwritten by the checkpointed data.
> - Unique task ids are not used by the dispatcher:
> https://issues.apache.org/jira/browse/MESOS-4737
> https://issues.apache.org/jira/browse/MESOS-3070
> This issue is the same in principle as the case with standalone mode where the master needs to re-launch drivers with a new appId (driverId) to deal with net partitions, but it affects mesos not spark, since we use 
> different driver ids anyway when we re-launch a driver.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org