whirr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrei Savu <savu.and...@gmail.com>
Subject Re: Starting HBASE Cluster - Unending whirr - IllegalStateException: The permission '72.205.25.214/32-1-2181-2181' has already been authorized on the specified group
Date Fri, 23 Dec 2011 05:36:42 GMT
Thanks David. I will perform some more checking over the weekend. I think
this is some sort of transient failure because before making the release
everything was working fine (maybe it has something to do with the service
start order - or lack of).

-- Andrei Savu

On Fri, Dec 23, 2011 at 1:21 AM, David Medinets <david.medinets@gmail.com>wrote:

> I have upgraded to v0.7.0 - as proven through 'whirr version' - using
> these commands:
>
> wget http://apache.mirrors.tds.net/whirr/whirr-0.7.0/whirr-0.7.0.tar.gz
> tar xvfz whirr-0.7.0.tar.gz
> export PATH=${PWD}/whirr-0.7.0/bin:$PATH
> chmod +x whirr-0.7.0/bin/*
>
> but I am seeing the same permission error. However, the exception is
> handled a bit cleaner. While the cluster is terminated due to the
> error, whirr still does not complete back to the command line.
>
> Please let me know if I can do anything to help resolve this.
>
> My hbase-ec2.properties file is now as follows. Notice that I don't
> specify the instance type or AMI:
>
> whirr.cluster-name=hbase
> whirr.instance-templates=1
> zookeeper+hadoop-namenode+hadoop-jobtracker+hbase-master,2
> hadoop-datanode+hadoop-tasktracker+hbase-regionserver
> whirr.provider=aws-ec2
> whirr.identity=${env:AWS_ACCESS_KEY_ID}
> whirr.credential=${env:AWS_SECRET_ACCESS_KEY}
> whirr.hbase.tarball.url=
> http://archive.apache.org/dist/hbase/hbase-0.89.20100924/hbase-0.89.20100924-bin.tar.gz
>
> whirr is automatically picking an instance type of m1.small with an
> AMI of ami-ab36fbc2. The three instances do start. And are terminated
> when the exception occurs.
>
>
> Still running whirr like this:
>
> whirr launch-cluster --config hbase-ec2.properties
>
> With the following result:
>
> Bootstrapping cluster
> Configuring template
> Configuring template
> Starting 1 node(s) with roles [zookeeper, hadoop-namenode,
> hadoop-jobtracker, hbase-master]
> Starting 2 node(s) with roles [hadoop-datanode, hadoop-tasktracker,
> hbase-regionserver]
>
> Nodes started: [[id=us-east-1/i-9ac71cf8, providerId=i-9ac71cf8,
> group=hbase, name=hbase-9ac71cf8, location=[id=us-east-1b, scope=ZONE,
> description=us-east-1b, parent=us-east-1, iso3166Codes=[US-VA],
> metadata={}], uri=null, imageId=us-east-1/ami-ab36fbc2, os=[name=null,
> family=ubuntu, version=10.04, arch=paravirtual, is64Bit=false,
>
> description=099720109477/ebs/ubuntu-images/ubuntu-lucid-10.04-i386-server-20110930],
> state=RUNNING, loginPort=22, hostname=domU-12-31-39-14-F5-FE,
> privateAddresses=[10.206.245.252], publicAddresses=[107.21.87.41],
> hardware=[id=m1.small, providerId=m1.small, name=null,
> processors=[[cores=1.0, speed=1.0]], ram=1740, volumes=[[id=null,
> type=LOCAL, size=150.0, device=/dev/sda2, durable=false,
> isBootDevice=false], [id=vol-617c160c, type=SAN, size=null,
> device=/dev/sda1, durable=true, isBootDevice=true]],
>
> supportsImage=And(ALWAYS_TRUE,Or(isWindows(),requiresVirtualizationType(paravirtual)),ALWAYS_TRUE,Not(is64Bit())),
> tags=[]], loginUser=ubuntu, userMetadata={Name=hbase-9ac71cf8},
> tags=[]]]
>
> Nodes started: [[id=us-east-1/i-94c71cf6, providerId=i-94c71cf6,
> group=hbase, name=hbase-94c71cf6, location=[id=us-east-1b, scope=ZONE,
> description=us-east-1b, parent=us-east-1, iso3166Codes=[US-VA],
> metadata={}], uri=null, imageId=us-east-1/ami-ab36fbc2, os=[name=null,
> family=ubuntu, version=10.04, arch=paravirtual, is64Bit=false,
>
> description=099720109477/ebs/ubuntu-images/ubuntu-lucid-10.04-i386-server-20110930],
> state=RUNNING, loginPort=22, hostname=domU-12-31-39-13-CC-50,
> privateAddresses=[10.201.207.190], publicAddresses=[107.21.74.44],
> hardware=[id=m1.small, providerId=m1.small, name=null,
> processors=[[cores=1.0, speed=1.0]], ram=1740, volumes=[[id=null,
> type=LOCAL, size=150.0, device=/dev/sda2, durable=false,
> isBootDevice=false], [id=vol-5b7c1636, type=SAN, size=null,
> device=/dev/sda1, durable=true, isBootDevice=true]],
>
> supportsImage=And(ALWAYS_TRUE,Or(isWindows(),requiresVirtualizationType(paravirtual)),ALWAYS_TRUE,Not(is64Bit())),
> tags=[]], loginUser=ubuntu, userMetadata={Name=hbase-94c71cf6},
> tags=[]], [id=us-east-1/i-98c71cfa, providerId=i-98c71cfa,
> group=hbase, name=hbase-98c71cfa, location=[id=us-east-1b, scope=ZONE,
> description=us-east-1b, parent=us-east-1, iso3166Codes=[US-VA],
> metadata={}], uri=null, imageId=us-east-1/ami-ab36fbc2, os=[name=null,
> family=ubuntu, version=10.04, arch=paravirtual, is64Bit=false,
>
> description=099720109477/ebs/ubuntu-images/ubuntu-lucid-10.04-i386-server-20110930],
> state=RUNNING, loginPort=22, hostname=domU-12-31-39-09-CD-73,
> privateAddresses=[10.210.210.129], publicAddresses=[107.22.36.203],
> hardware=[id=m1.small, providerId=m1.small, name=null,
> processors=[[cores=1.0, speed=1.0]], ram=1740, volumes=[[id=null,
> type=LOCAL, size=150.0, device=/dev/sda2, durable=false,
> isBootDevice=false], [id=vol-597c1634, type=SAN, size=null,
> device=/dev/sda1, durable=true, isBootDevice=true]],
>
> supportsImage=And(ALWAYS_TRUE,Or(isWindows(),requiresVirtualizationType(paravirtual)),ALWAYS_TRUE,Not(is64Bit())),
> tags=[]], loginUser=ubuntu, userMetadata={Name=hbase-98c71cfa},
> tags=[]]]
>
> Authorizing firewall ingress to [us-east-1/i-9ac71cf8] on ports [2181]
> for [72.205.25.214/32]
> The permission '72.205.25.214/32-1-2181-2181' has already been
> authorized on the specified group
> Unable to start the cluster. Terminating all nodes.
>

Mime
View raw message