[
https://issues.apache.org/jira/browse/SPARK-22336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan X. Huynh updated SPARK-22336:
-----------------------------------
Description:
In Mesos cluster mode, spark-submit passes all local MESOS_xxx env vars to the
Dispatcher (via RestSubmissionClient). When these env vars are later set in the
Driver task, they overwrite existing MESOS_xxx env vars, such as
MESOS_FRAMEWORK_ID and MESOS_EXECUTOR_ID, that are needed to run correctly on
MESOS. This makes it impossible to run spark-submit from Chronos, or any Mesos
task, because the resulting driver will inherit the wrong MESOS_xxx and fail
right away.
A Mesos issue reporting the same behavior:
https://github.com/mesos/chronos/issues/707
was:
In Mesos cluster mode, spark-submit passes all local MESOS_xxx env vars to the
Dispatcher (via RestSubmissionClient). When these env vars are later set in the
Driver task, they overwrite existing MESOS_xxx env vars, such as
MESOS_FRAMEWORK_ID and MESOS_EXECUTOR_ID, that are needed to run correctly on
MESOS. This makes it impossible to run spark-submit from Chronos, or any Mesos
task, because the resulting driver will inherit the wrong MESOS_xxx fail right
away.
A Mesos issue reporting the same behavior:
https://github.com/mesos/chronos/issues/707
> When spark-submit cluster mode is run from a Mesos task, the job fails
> ----------------------------------------------------------------------
>
> Key: SPARK-22336
> URL: https://issues.apache.org/jira/browse/SPARK-22336
> Project: Spark
> Issue Type: Bug
> Components: Mesos
> Affects Versions: 2.0.2
> Environment: Mesos
> Reporter: Susan X. Huynh
>
> In Mesos cluster mode, spark-submit passes all local MESOS_xxx env vars to
> the Dispatcher (via RestSubmissionClient). When these env vars are later set
> in the Driver task, they overwrite existing MESOS_xxx env vars, such as
> MESOS_FRAMEWORK_ID and MESOS_EXECUTOR_ID, that are needed to run correctly on
> MESOS. This makes it impossible to run spark-submit from Chronos, or any
> Mesos task, because the resulting driver will inherit the wrong MESOS_xxx and
> fail right away.
> A Mesos issue reporting the same behavior:
> https://github.com/mesos/chronos/issues/707
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
