You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xiangrui Meng (JIRA)" <ji...@apache.org> on 2014/05/23 00:39:01 UTC

[jira] [Resolved] (SPARK-1905) Issues with `spark-submit`

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

Xiangrui Meng resolved SPARK-1905.
----------------------------------

    Resolution: Duplicate

> Issues with `spark-submit`
> --------------------------
>
>                 Key: SPARK-1905
>                 URL: https://issues.apache.org/jira/browse/SPARK-1905
>             Project: Spark
>          Issue Type: Task
>          Components: Deploy
>            Reporter: Xiangrui Meng
>
> Main JIRA for tracking the issues with `spark-submit` in different deploy modes.
> For deploy modes, `client` means running driver on the client side (outside the cluster), while `cluster` means running driver inside the cluster. Ideally, we want to have `spark-submit` support all deploy modes in a unified way, which include
> * documented
> ** local client
> ** standalone client
> ** standalone cluster
> ** yarn client
> ** yarn cluster
> ** mesos client
> * undocumented (for testing only)
> ** local cluster
> * not supported
> ** mesos cluster
> In each deploy mode, we also need to test launching python jobs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)