In my experience you need

whirr.run-url-base=http://name-of-my-bucket-with-customized-scripts/
whirr.hadoop-install-runurl=cloudera/cdh/install

and then you *also* need to have a copy of sun/java/install in that same bucket.

And both of those scripts need to be public-readable.

So in the end you should be able to do
curl 
http://name-of-my-bucket-with-customized-scripts.s3.amazonaws.com/cloudera/cdh/install

and 
curl 
http://name-of-my-bucket-with-customized-scripts.s3.amazonaws.com/sun/java/install

Even if you haven't customizied sun/java/install, it needs to be there.

If you do all that, the scripts will run and you will have the versions you 
asked for.

`hadoop version` on the name node then says, in my case:

Hadoop 0.20.2-CDH3B4

On Mar 7, 2011, at 12:41 PM, Saptarshi Guha wrote:

> Hi,
> Fixed the security slip up. Did the hadoop version thing and got this
> 
> [root@domU-12-31-39-0B-CC-41 ~]# hadoop version
> Hadoop 0.20.2
> Subversion https://svn.apache.org/repos/asf/hadoop/common/branches/branch-0.20
> -r 911707
> Compiled by chrisdo on Fri Feb 19 08:07:34 UTC 2010
> 
> So i guess its not CDH.
> 
> Thanks
> Saptarshi
> 
> 
> On Mon, Mar 7, 2011 at 9:22 AM, Saptarshi Guha
> <saptar...@revolutionanalytics.com> wrote:
>> dear me! thanks, will do right away.
>> 
>> 
>> On Mon, Mar 7, 2011 at 1:46 AM, Sebastian Schoenherr
>> <sebastian.schoenh...@uibk.ac.at> wrote:
>>> Hi Saptarshi,
>>> Try to execute "hadoop version" on your namenode, if the output is Hadoop
>>> 0.20.2-CDH3B4, the current cloudera distribution has been installed.
>>> Btw, I would recommend to set your current Access Key ID and Secret Key
>>> inactive, since you posted it in your prop file.
>>> cheers
>>> sebastian
>>> 
>>> On 06.03.2011 06:54, Saptarshi Guha wrote:
>>>> 
>>>> Hello,
>>>> 
>>>> I did git clone of the latest whirr and copied cloudera scripts into
>>>> the script directory (copied over
>>>> from whirr-0.3-incubating).
>>>> 
>>>> My properties file is at the end of this email.
>>>> 
>>>> However, I don't think the scripts are being run because the jobtracker
>>>> is the default Apache hadoop jobtracker and not the cloudera jobtracker.
>>>> 
>>>> Have i missed something?
>>>> 
>>>> Thanks in advance
>>>> 
>>>> Saptarshi
>>>> 
>>>> ## Properties
>>>> 
>>>> 
>>>> whirr.cluster-name=revotesting
>>>> whirr.service-name=hadoop
>>>> whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker,2
>>>> hadoop-datanode+hadoop-tasktracker
>>>> whirr.provider=aws-ec2
>>>> whirr.identity= AKIAI3FUFFXAPYLE7CJA
>>>> whirr.credential= 2Yq3Ar2HSxK/hbwZHs6aN6yrh0yfGNSPTpVw3t2n
>>>> whirr.location-id=us-east-1
>>>> whirr.hardware-id=c1.xlarge
>>>> 
>>>> ## Rightscales CentOS AMI
>>>> 
>>>> http://support.rightscale.com/18-Release_Notes/02-AMI/RightImages_Release_Notes
>>>> jclouds.ec2.ami-owners=411009282317
>>>> whirr.image-id=us-east-1/ami-ccb35ea5
>>>> 
>>>> whirr.hadoop-install-runurl=cloudera/cdh/install
>>>> whirr.hadoop-configure-runurl=cloudera/cdh/post-configure
>>> 
>>> 
>> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to