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] Resolved: (HBASE-2080) [EC2] Support multivolume local instance storage
Date Thu, 31 Dec 2009 10:52:29 GMT

     [ https://issues.apache.org/jira/browse/HBASE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell resolved HBASE-2080.
-----------------------------------

    Resolution: Fixed

> [EC2] Support multivolume local instance storage
> ------------------------------------------------
>
>                 Key: HBASE-2080
>                 URL: https://issues.apache.org/jira/browse/HBASE-2080
>             Project: Hadoop HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 0.20.3, 0.21.0
>
>         Attachments: HBASE-2080.patch
>
>
> The (old) Hadoop EC2 scripts we used as a basis for our scripts do not properly handle
instance types that have their local storage attached as multiple volumes. The AMI build script
uses Amazon's latest Fedora 8 AMI as a base, which does not automatically mount instance storage
on multiple volumes either. 
> We recommend use of two instance types:
> - c1.medium for zookeeper, which has one vdisk of 340 GB as /dev/sdb mounted on /mnt
by the base image
> - c1.xlarge for master and slaves, which have four vdisks of 420 GB as /dev/sd[bcde],
only one of which is mounted on /mnt by the base image
> Additionally, the m1.xlarge instance type, which a user might use anyway, has two vdisks
of 420 GB as /dev/sd[bc], only one of which is mounted on /mnt by the base image. 
> The hbase-ec2-init-remote.sh script should probe for all available instance storage devices,
mount them, and update the DataNode configuration appropriately. 

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


Mime
View raw message