Kris Jirapinyo wrote:
Why would you lose the locality of storage-per-machine if one EBS volume is
mounted to each machine instance? When that machine goes down, you can just
restart the instance and re-mount the exact same volume. I've tried this
idea before successfully on a 10 node cluster on EC2, and didn't see any
adverse performance effects--
I was thinking more of S3 FS, which is remote-ish and write times measurable
and actually amazon claims that EBS I/O should
be even better than the instance stores.
Assuming the transient filesystems are virtual disks (and not physical
disks that get scrubbed, formatted and mounted on every VM
instantiation), and also assuming that EBS disks are on a SAN in the
same datacentre, this is probably true. Disk IO performance in virtual
disks is currently pretty slow as you are navigating through >1
filesystem, and potentially seeking at lot, even something that appears
unfragmented at the VM level
The only concerns I see are that
you need to pay for EBS storage regardless of whether you use that storage
or not. So, if you have 10 EBS volumes of 1 TB each, and you're just
starting out with your cluster so you're using only 50GB on each EBS volume
so far for the month, you'd still have to pay for 10TB worth of EBS volumes,
and that could be a hefty price for each month. Also, currently EBS needs
to be created in the same availability zone as your instances, so you need
to make sure that they are created correctly, as there is no direct
migration of EBS to different availability zones.
View EBS as renting space in SAN and it starts to make sense.
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/