diff options
| author | Matei Zaharia <matei@eecs.berkeley.edu> | 2013-11-12 16:26:09 -0800 |
|---|---|---|
| committer | Matei Zaharia <matei@eecs.berkeley.edu> | 2013-11-12 16:26:09 -0800 |
| commit | 87f2f4e5c2812351cdd1b2e35e2b12f62eeb3fdc (patch) | |
| tree | 91cf7995d20e600c8526ad036685fe6cbe08aa3c /project | |
| parent | b8bf04a085162478a64ca5d7be15d1af2f6a930e (diff) | |
| parent | bc9f7eacb94e05ec089ee7a2d130a2e8a9e54c64 (diff) | |
| download | spark-87f2f4e5c2812351cdd1b2e35e2b12f62eeb3fdc.tar.gz spark-87f2f4e5c2812351cdd1b2e35e2b12f62eeb3fdc.tar.bz2 spark-87f2f4e5c2812351cdd1b2e35e2b12f62eeb3fdc.zip | |
Merge pull request #153 from ankurdave/stop-spot-cluster
Enable stopping and starting a spot cluster
Clusters launched using `--spot-price` contain an on-demand master and spot slaves. Because EC2 does not support stopping spot instances, the spark-ec2 script previously could only destroy such clusters.
This pull request makes it possible to stop and restart a spot cluster.
* The `stop` command works as expected for a spot cluster: the master is stopped and the slaves are terminated.
* To start a stopped spot cluster, the user must invoke `launch --use-existing-master`. This launches fresh spot slaves but resumes the existing master.
Diffstat (limited to 'project')
0 files changed, 0 insertions, 0 deletions