Whirr and HBase

Hi, I am trying to run an HBase small cluster using Whirr 0.3.0-incubating and (since it does not start HBase master or it does not install Hadoop correctly) Whirr from trunk. When I run it from trunk with a recipe very similar to the one provided in the recipes folder, I see these errors in the

Re: Whirr and HBase

Could you share the recipe? I want to try to replicate the issue on my computer. On Tue, Feb 1, 2011 at 5:32 PM, Paolo Castagna wrote: > Hi, > I am trying to run an HBase small cluster using Whirr 0.3.0-incubating > and (since it does not start HBase master or it does not install Hadoop > correct

Re: Whirr and HBase

Andrei Savu wrote: Could you share the recipe? I want to try to replicate the issue on my computer. whirr.cluster-name=myhbase whirr.instance-templates=1 zk+nn+jt+hbase-master,3 dn+tt+hbase-regionserver whirr.hadoop-install-runurl=cloudera/cdh/install whirr.hadoop-confi

Re: Whirr and HBase

Are you sure you are running the latest trunk? I know that a similar bug was fixed some time ago (guarding against existing user accounts) The recipe looks good do me. I will give it a try and get back to you. On Tue, Feb 1, 2011 at 5:53 PM, Paolo Castagna wrote: > Andrei Savu wrote: >> >> Could

Re: Whirr and HBase

Hi, Talking to Paolo on IRC right now. Looks like the scripts are outdated. I need to check what is where, i.e. trunk vs. 0.3.0. Lars On Tue, Feb 1, 2011 at 4:53 PM, Paolo Castagna wrote: > Andrei Savu wrote: >> >> Could you share the recipe? I want to try to replicate the issue on my >> comput

Re: Whirr and HBase

Try removing the CDH lines. I don't think that this combination works yet. Tom On Feb 1, 2011 7:53 AM, "Paolo Castagna" wrote: > Andrei Savu wrote: >> Could you share the recipe? I want to try to replicate the issue on my computer. > > > whirr.cluster-name=myhbase > whirr

Re: Whirr and HBase

Tom White wrote: Try removing the CDH lines. I don't think that this combination works yet. Thanks Tom. Done. But, I have a different error in whirr.log: 2011-02-01 16:11:09,468 DEBUG [jclouds.compute] (user thread 2) << stderr from computeserv as ubuntu@184.72.166.164 + configure_hbase +

Re: Whirr and HBase

Oh darn, spot on, didn't see those. Yeah, CDH support for HBase is still pending (but coming for sure)! On Tue, Feb 1, 2011 at 5:05 PM, Tom White wrote: > Try removing the CDH lines. I don't think that this combination works yet. > > Tom > > On Feb 1, 2011 7:53 AM, "Paolo Castagna" > wrote: >> A

Re: Whirr and HBase

Lars George wrote: Oh darn, spot on, didn't see those. Yeah, CDH support for HBase is still pending (but coming for sure)! Sorry, I read the comment "uncomment out these lines to run CDH". ;-) Anyway, I still have problems. This is the latest recipe I have tried: whirr.cluster-na

Re: Whirr and HBase

Paolo, You can find debug output on the instances in subdirectories of /tmp. Cheers, Tom On Tue, Feb 1, 2011 at 8:49 AM, Paolo Castagna wrote: > Lars George wrote: >> >> Oh darn, spot on, didn't see those. Yeah, CDH support for HBase is >> still pending (but coming for sure)! > > Sorry, I read

Re: Whirr and HBase

Tom White wrote: Paolo, You can find debug output on the instances in subdirectories of /tmp. Hi Tom, thanks, good to know. This is what I see on the machine which should run nn+jt+hbase-master: /tmp/runscript/stderr.log: [...] + curl --retry 3 --silent --show-error --fail -O http://archiv

Re: Whirr and HBase

There is an open issue for this WHIRR-207 [1] and unfortunately no patch available. [1] https://issues.apache.org/jira/browse/WHIRR-207 On Tue, Feb 1, 2011 at 10:36 PM, Paolo Castagna < castagna.li...@googlemail.com> wrote: > Tom White wrote: > >> Paolo, >> >> You can find debug output on the in

Re: Whirr and HBase

Andrei Savu wrote: There is an open issue for this WHIRR-207 [1] and unfortunately no patch available. Thanks, I did not see that. I have tried again... this time, HBase has been downloaded successfully. But, HBase master failed to start, from /var/log/hbase/logs/hbase-hadoop-master-ip-10-

Re: Whirr and HBase

This could be related to the order in which services are started. There is an open issue related to this nondeterministic behavior: https://issues.apache.org/jira/browse/WHIRR-221 I not sure if this is related to the problem you are facing. I don't

Re: Whirr and HBase

Andrei Savu wrote: This could be related to the order in which services are started. There is an open issue related to this nondeterministic behavior: https://issues.apache.org/jira/browse/WHIRR-221 Yes, it could well be this the problem. However, I was searching for Hadoop on the same machi

Re: Whirr and HBase

See bellow. On Wed, Feb 2, 2011 at 10:30 AM, Paolo Castagna < castagna.li...@googlemail.com> wrote: > Andrei Savu wrote: > >> This could be related to the order in which services are started. >> There is an open issue related to this nondeterministic behavior: >> https://issues.apache.org/jira/br

Re: Whirr and HBase

Andrei Savu wrote: See bellow. On Wed, Feb 2, 2011 at 10:30 AM, Paolo Castagna mailto:castagna.li...@googlemail.com>> wrote: Andrei Savu wrote: This could be related to the order in which services are started. There is an open issue related to this nondeterministic beh

Re: Whirr and HBase

Paolo, I just wanted to let you know that it seems like the trunk is broken. I am unable to run the integration tests for CDH and Hadoop. This could be related to the failures you are seeing. The same tests are working on the 0.3.0 branch. Sorry for all the trouble. I will try to track this down

Re: Whirr and HBase

Hi Andrei, thanks for letting me know. I did try to use the 0.3.0 branch as well, but I had problems with that as well, I think there my problems were related to failures of downloading the HBase tar.gz (but, again... I had different set of problems, I am not 100% confident on this). I used trun

Re: Whirr and HBase

Paolo, the trunk should be working now. Yesterday I have successfully run all the unit and integration tests. We are also using a new version of jclouds now. On Wed, Feb 2, 2011 at 4:31 PM, Paolo Castagna wrote: > Hi Andrei, > thanks for letting me know. > > I did try to use the 0.3.0 branch as w