You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2015/07/19 11:44:04 UTC

[jira] [Resolved] (SPARK-9007) start-slave.sh changed API in 1.4 and the documentation got updated to mention the old API

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

Sean Owen resolved SPARK-9007.
------------------------------
    Resolution: Duplicate

Unless I'm mistaken the change envisioned here was already done in SPARK-8395  https://github.com/apache/spark/commit/f005be02730db315e2a6d4dbecedfd2562b9ef1f

> start-slave.sh changed API in 1.4 and the documentation got updated to mention the old API
> ------------------------------------------------------------------------------------------
>
>                 Key: SPARK-9007
>                 URL: https://issues.apache.org/jira/browse/SPARK-9007
>             Project: Spark
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.4.0
>            Reporter: Jesper Lundgren
>            Priority: Trivial
>
> In Spark version < 1.4 start-slave.sh accepted two parameters. worker# and a list of master addresses.
> With Spark 1.4 the start-slave.sh worker# parameter was removed, which broke our custom standalone cluster setup.
> With Spark 1.4 the documentation was also updated to mention spark-slave.sh (not previously mentioned), but it describes the old API.



--
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