GitHub user thvasilo opened a pull request:
https://github.com/apache/spark/pull/4916
[EC2] [SPARK-6188] Instance types can be mislabeled when re-starting
cluster with default arguments
As described in https://issues.apache.org/jira/browse/SPARK-6188 and
discovered in https://issues.apache.org/jira/browse/SPARK-5838.
When re-starting a cluster, if the user does not provide the instance
types, which is the recommended behavior in the docs currently, the instance
will be assigned the default type m1.large. This then affects the setup of the
machines.
This solves this by getting the instance types from the existing instances,
and overwriting the default options.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/thvasilo/spark
SPARK-6188]-Instance-types-can-be-mislabeled-when-re-starting-cluster-with-default-arguments
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/4916.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4916
----
commit 3ebd52a8ce5c655e133387d99ea38147cf10efff
Author: Theodore Vasiloudis <[email protected]>
Date: 2015-03-05T17:08:59Z
Make sure that the instance type is correct when relaunching a cluster.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
