Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/4916#issuecomment-77564954
@thvasilo can you clarify what flow you are seeing this behavior for? I
can't reproduce the issue you're reporting.
Here's what I tried:
1. Launch a cluster, setting the instance type to `m3.large`, which is
different from the default instance type.
```
./spark-ec2 launch "spark-test" \
--instance-type m3.large \
--slaves 1 \
...
```
2. Stop the cluster.
```
./spark-ec2 stop "spark-test" \
...
```
3. Start the cluster without specifying the instance type.
```
./spark-ec2 start "spark-test" \
...
```
My cluster came back up with the instance types I originally specified,
which is the expected behavior.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
