You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Eugene Marinelli (Updated) (JIRA)" <ji...@apache.org> on 2012/01/09 00:26:39 UTC

[jira] [Updated] (WHIRR-470) Regionservers fail when starting cdh3 versions of hadoop and hbase

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

Eugene Marinelli updated WHIRR-470:
-----------------------------------

    Description: 
hadoop-ec2-0.90.properties:
{code}
whirr.cluster-name=hbase-0.90
whirr.instance-templates=1 zookeeper+hadoop-namenode+hadoop-jobtracker+hbase-master,4 hadoop-datanode+hadoop-tasktracker+hbase-regionserver
hbase-site.dfs.replication=4
whirr.provider=aws-ec2
whirr.identity=${env:AWS_ACCESS_KEY_ID}
whirr.credential=${env:AWS_SECRET_ACCESS_KEY}
whirr.hardware-id=c1.xlarge

# Ubuntu 10.04 LTS Lucid. See http://alestic.com/                                                                                      
whirr.image-id=us-east-1/ami-da0cf8b3

whirr.location-id=us-east-1
whirr.hbase.tarball.url=http://archive.cloudera.com/cdh/3/hbase-0.90.4-cdh3u2.tar.gz                                                   
whirr.hadoop.tarball.url=http://archive.cloudera.com/cdh/3/hadoop-0.20.2-cdh3u2.tar.gz                                                 
{code}

{code}
whirr launch-cluster --config hadoop-ec2-0.90.properties
{code}

The cluster launches, but the region servers are dead on arrival. I'm able to start them manually later via "/usr/local/hbase-0.90.4-cdh3u2/bin/hbase regionserver start". The regionserver log from one of the nodes is attached.

  was:
hadoop-ec2-0.90.properties:
{code}
whirr.cluster-name=hbase-0.90

# Change the number of machines in the cluster here                                                                                    
whirr.instance-templates=1 zookeeper+hadoop-namenode+hadoop-jobtracker+hbase-master,4 hadoop-datanode+hadoop-tasktracker+hbase-regionserver

# replication level should not be higher than number of data nodes                                                                     
hbase-site.dfs.replication=4

# For EC2 set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables.                                                       
whirr.provider=aws-ec2
whirr.identity=${env:AWS_ACCESS_KEY_ID}
whirr.credential=${env:AWS_SECRET_ACCESS_KEY}

# The size of the instance to use. See http://aws.amazon.com/ec2/instance-types/                                                       
whirr.hardware-id=c1.xlarge
# Ubuntu 10.04 LTS Lucid. See http://alestic.com/                                                                                      
whirr.image-id=us-east-1/ami-da0cf8b3
# If you choose a different location, make sure whirr.image-id is updated too                                                          
whirr.location-id=us-east-1

# By default use the user system SSH keys. Override them here.                                                                         
# whirr.private-key-file=${sys:user.home}/.ssh/id_rsa                                                                                  
# whirr.public-key-file=${whirr.private-key-file}.pub                                                                                  

# The HBase version to use.                                                                                                            
#whirr.hbase.tarball.url=http://apache.cu.be/hbase/hbase-0.90.4/hbase-0.90.4.tar.gz                                                    
whirr.hbase.tarball.url=http://archive.cloudera.com/cdh/3/hbase-0.90.4-cdh3u2.tar.gz                                                   

# The Hadoop version to use. See http://hbase.apache.org/book/hadoop.html                                                              
# The default Hadoop version used by Whirr does not fulfill the HBase 0.90.x requirements.                                             
# Whirr will replace the hadoop-core jar in HBase with the one from the actually installed Hadoop.                                     
# This example uses Cloudera's CDH3.                                                                                                   
whirr.hadoop.tarball.url=http://archive.cloudera.com/cdh/3/hadoop-0.20.2-cdh3u2.tar.gz                                                 
{code}

{code}
whirr launch-cluster --config hadoop-ec2-0.90.properties
{code}

The cluster launches, but the region servers are dead on arrival. I'm able to start them manually later via "/usr/local/hbase-0.90.4-cdh3u2/bin/hbase regionserver start". The regionserver log from one of the nodes is attached.

    
> Regionservers fail when starting cdh3 versions of hadoop and hbase
> ------------------------------------------------------------------
>
>                 Key: WHIRR-470
>                 URL: https://issues.apache.org/jira/browse/WHIRR-470
>             Project: Whirr
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>            Reporter: Eugene Marinelli
>         Attachments: hbase-hadoop-regionserver-ip-10-47-30-12.log
>
>
> hadoop-ec2-0.90.properties:
> {code}
> whirr.cluster-name=hbase-0.90
> whirr.instance-templates=1 zookeeper+hadoop-namenode+hadoop-jobtracker+hbase-master,4 hadoop-datanode+hadoop-tasktracker+hbase-regionserver
> hbase-site.dfs.replication=4
> whirr.provider=aws-ec2
> whirr.identity=${env:AWS_ACCESS_KEY_ID}
> whirr.credential=${env:AWS_SECRET_ACCESS_KEY}
> whirr.hardware-id=c1.xlarge
> # Ubuntu 10.04 LTS Lucid. See http://alestic.com/                                                                                      
> whirr.image-id=us-east-1/ami-da0cf8b3
> whirr.location-id=us-east-1
> whirr.hbase.tarball.url=http://archive.cloudera.com/cdh/3/hbase-0.90.4-cdh3u2.tar.gz                                                   
> whirr.hadoop.tarball.url=http://archive.cloudera.com/cdh/3/hadoop-0.20.2-cdh3u2.tar.gz                                                 
> {code}
> {code}
> whirr launch-cluster --config hadoop-ec2-0.90.properties
> {code}
> The cluster launches, but the region servers are dead on arrival. I'm able to start them manually later via "/usr/local/hbase-0.90.4-cdh3u2/bin/hbase regionserver start". The regionserver log from one of the nodes is attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira