Github user mrdrozdov commented on the pull request:
https://github.com/apache/spark/pull/5172#issuecomment-85690344
Launching/Accessing/Destroy clusters using spark-ec2 should be sufficient
for this change. Could run the following basic flow to double check that
everything's in order:
```
# Basic
./spark-ec2 -k <key_name> -i <key_path> -s 1 launch sparky
./spark-ec2 -k <key_name> -i <key_path> login sparky
./spark-ec2 -k <key_name> -i <key_path> destroy sparky
# Bad AMI (HVM)
./spark-ec2 -k <key_name> -i <key_path> -s 1 -a ami-35b1885c launch sparky
# Custom AMI
./spark-ec2 -k <key_name> -i <key_path> -s 1 --region=us-east-1
--zone=us-east-1d -a ami-5bb18832 launch sparky
```
---
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]
