hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1980) [EC2] EBS support
Date Fri, 04 Dec 2009 17:36:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786018#action_12786018

Andrew Purtell commented on HBASE-1980:

Amazon announced today a new capability for optionally starting up instances backed by EBS

*Amazon EC2 Boot from Amazon EBS*
Amazon EC2 has also announced the ability to boot instances directly from Amazon EBS snapshots,
providing significantly increased flexibility in how customers can manage their instances.
You can still save an Amazon Machine Image (AMI) in an Amazon S3 bucket and boot it from the
local instance store, but you can now also choose to save AMIs as Amazon EBS snapshots and
boot directly from an Amazon EBS volume. When an instance is booted from an Amazon EBS snapshot,
the root partition of the instance is created on an Amazon EBS volume. Instances booted from
Amazon EBS volumes can be stopped and later restarted, preserving any of the state that is
saved to your volume and allowing you to modify some properties of your instances while it
is stopped. For example, you can change your instance size or update the kernel it is using,
or attach your root partition to a different running instance, making it easier to do debugging
when you are creating new boot images. When booting from an Amazon EBS volume, AMIs and root
partitions are no longer limited to 10GB, but can be up to 1TB in size, enabling significantly
more complex images. Additionally, you are not charged for stopped instance hours and you
will only incur charges for your Amazon EBS volumes while your instance is stopped, allowing
you to reduce your Amazon EC2 costs when you do not need your instances running. Customers
can now use a newly launched API that makes it easy to bundle images without using the command
line tools, and can also take advantage of the fact that the content of an Amazon EBS volume
is available to the instance immediately on volume creation which can lead to much faster
instance boot times. 

Could be one way to accomplish this.

> [EC2] EBS support
> -----------------
>                 Key: HBASE-1980
>                 URL: https://issues.apache.org/jira/browse/HBASE-1980
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 0.20.3, 0.21.0
> Tweak HBase EC2 scripts to provide an option for backing HDFS with EBS volumes instead
of plain instance storage. 
> Accept a list of EBS volume identifiers to assign to datanodes or dynamically create
them on behalf of the user. Use ZK to coordinate volume mounts on the datanodes. 
> Will also require terminate-hbase-cluster to do a clean HBase shutdown if EBS volumes
are used rather than just ec2-terminate-instance. Presumably this option would be used to
persist data across cluster instances. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message