On Tue, Oct 4, 2011 at 4:54 PM, Jim R. Wilson <[email protected]>wrote:
> Thanks Andrei, > > Would using REST allow me to connect via the hbase shell? > I don't think so. Right now the only to run the shell way is to login to a cluster machine. > > Using the noop role, does it matter whether that's defined before or after > the other roles? > The noop role is designed to allow you to start another machine that has no specific role. E.g whirr.instance-templates = 1 hadoop-namenode+hadoop-jobtracker, 1 hadoop-datanode+hadoop-tasktracker, 1 noop You can use that machine to deploy your tools as needed. > > -- Jim > > > On Tue, Oct 4, 2011 at 9:49 AM, Andrei Savu <[email protected]> wrote: > >> This is a known issue and we don't have a workaround. >> >> Would it be possible to use the rest interface from the local machine? How >> are you planning to use HBase? >> >> As a side note you can start in the same security group an "empty" machine >> using the noop role. >> >> -- Andrei Savu / andreisavu.ro >> >> >> On Tue, Oct 4, 2011 at 4:43 PM, Jim R. Wilson <[email protected]>wrote: >> >>> Hi all, >>> >>> First, let me thank you for adding 0.90.3 support to Whirr 0.6.0 - this >>> is a big help! >>> >>> I'm trying to run a small demo cluster based on the 0.90.3-ec2 recipe. >>> The cluster seems to be working, because when I SSH into a node and use the >>> hbase shell (/usr/local/hbase-0.90.3/bin/hbase shell), commands seem to work >>> as expected. >>> >>> However, when I try to connect from my local host by using the generated >>> hbase-site.xml over the proxy tunnel created by hbase-proxy.sh, I get this >>> error message: >>> >>> hbase(main):001:0> status >>> 11/10/04 09:37:12 ERROR hbase.HServerAddress: Could not resolve the DNS >>> name of domU-<...>.compute-1.internal:60000 >>> >>> ERROR: java.lang.IllegalArgumentException: Could not resolve the DNS name >>> of domU-<...>.compute-1.internal:60000 >>> >>> Am I doing something wrong? Is this a known issue? Thanks, >>> >>> -- Jim R Wilson (jimbojw) >>> >> >> >
