diff options
| author | Daniel Darabos <darabos.daniel@gmail.com> | 2014-09-01 22:14:28 -0700 |
|---|---|---|
| committer | Matei Zaharia <matei@databricks.com> | 2014-09-01 22:16:42 -0700 |
| commit | 44d3a6a75209370b1648e2dfedaa4c895923dae5 (patch) | |
| tree | 10f5c85f31813c0bcdffc05db88dbdde5893fb28 /project/MimaExcludes.scala | |
| parent | db160676c56de54efc4d42c6466847c2c3b6a963 (diff) | |
| download | spark-44d3a6a75209370b1648e2dfedaa4c895923dae5.tar.gz spark-44d3a6a75209370b1648e2dfedaa4c895923dae5.tar.bz2 spark-44d3a6a75209370b1648e2dfedaa4c895923dae5.zip | |
[SPARK-3342] Add SSDs to block device mapping
On `m3.2xlarge` instances the 2x80GB SSDs are inaccessible if not added to the block device mapping when the instance is created. They work when added with this patch. I have not tested this with other instance types, and I do not know much about this script and EC2 deployment in general. Maybe this code needs to depend on the instance type.
The requirement for this mapping is described in the AWS docs at:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/InstanceStorage.html#InstanceStore_UsageScenarios
"For M3 instances, you must specify instance store volumes in the block
device mapping for the instance. When you launch an M3 instance, we
ignore any instance store volumes specified in the block device mapping
for the AMI."
Author: Daniel Darabos <darabos.daniel@gmail.com>
Closes #2081 from darabos/patch-1 and squashes the following commits:
1ceb2c8 [Daniel Darabos] Use %d string interpolation instead of {}.
a1854d7 [Daniel Darabos] Only specify ephemeral device mapping for M3.
e0d9e37 [Daniel Darabos] Create ephemeral device mapping based on get_num_disks().
6b116a6 [Daniel Darabos] Add SSDs to block device mapping
Diffstat (limited to 'project/MimaExcludes.scala')
0 files changed, 0 insertions, 0 deletions