Please file a JIRA - email tends to get out of focus. On Mon, Jan 30, 2012 at 3:17 PM, Tim Robertson <[email protected]>wrote:
> What would be correct protocol Andrei? Want me to file the Jira or > would I just be polluting? > > > > On Mon, Jan 30, 2012 at 2:06 PM, Andrei Savu <[email protected]> > wrote: > > I think this is yet another DNS related failure - we really need to > improve > > this for 0.7.1. Thanks for reporting! > > > > > > On Mon, Jan 30, 2012 at 3:03 PM, Tim Robertson < > [email protected]> > > wrote: > >> > >> Hi all, > >> > >> I have been using trunk and 0.7.0.2 trying to get HBase running on EC2 > >> but having a few teething issues. > >> > >> Running a 1 master, 3 node cluster, I see on the Hadoop task trackers > >> the following hosts: > >> > >> 1) domU-12-31-39-0B-C1-81.compute-1.internal > >> 2) ip-10-66-197-215.ec2.internal > >> 3) domU-12-31-39-0E-F2-41.compute-1.internal > >> > >> This is consistent with both the trunk (today) and 0.7.0.2, and all > >> tasks on node 2) above then fail. > >> > >> My config is the following: > >> whirr.cluster-name=hbase > >> whirr.instance-templates=1 > >> zookeeper+hadoop-namenode+hadoop-jobtracker+hbase-master,3 > >> 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.hardware-id=c1.xlarge > >> whirr.image-id=us-east-1/ami-da0cf8b3 > >> whirr.location-id=us-east-1 > >> > >> Should I file a Jira, or am I doing something wrong? > >> > >> Cheers, > >> Tim > > > > >
