You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2015/03/05 18:19:38 UTC
[jira] [Commented] (SPARK-6188) Instance types can be mislabeled
when re-starting cluster with default arguments
[ https://issues.apache.org/jira/browse/SPARK-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349115#comment-14349115 ]
Apache Spark commented on SPARK-6188:
-------------------------------------
User 'thvasilo' has created a pull request for this issue:
https://github.com/apache/spark/pull/4916
> Instance types can be mislabeled when re-starting cluster with default arguments
> --------------------------------------------------------------------------------
>
> Key: SPARK-6188
> URL: https://issues.apache.org/jira/browse/SPARK-6188
> Project: Spark
> Issue Type: Bug
> Components: EC2
> Affects Versions: 1.0.2, 1.1.0, 1.1.1, 1.2.0, 1.2.1
> Reporter: Theodore Vasiloudis
> Priority: Minor
>
> This was discovered when investigating https://issues.apache.org/jira/browse/SPARK-5838.
> In short, when restarting a cluster that you launched with an alternative instance type, you have to provide the instance type(s) again in the "/spark-ec2 -i <key-file> --region=<ec2-region> start <cluster-name>" command. Otherwise it gets set to the default m1.large.
> This then affects the setup of the machines.
> I'll submit a pull request that takes cares of this, without the user needing to provide the instance type(s) again.
--
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