You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrei Savu (Commented) (JIRA)" <ji...@apache.org> on 2012/03/16 15:15:41 UTC

[jira] [Commented] (WHIRR-560) starting instances fails for cloudera cdh3u2

    [ https://issues.apache.org/jira/browse/WHIRR-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231205#comment-13231205 ] 

Andrei Savu commented on WHIRR-560:
-----------------------------------

Does it work if you use a larger instance? I think this is the root cause here. 
                
> starting instances fails for cloudera cdh3u2
> --------------------------------------------
>
>                 Key: WHIRR-560
>                 URL: https://issues.apache.org/jira/browse/WHIRR-560
>             Project: Whirr
>          Issue Type: Bug
>          Components: service/cdh
>    Affects Versions: 0.7.1
>            Reporter: Sean Zhang
>         Attachments: badlogs.tar.gz
>
>
> Seems to me that the installation of the openJDK failed. The failure is not consistent. It fails for me for more than 50% of times. It only fails when "whirr.env.repo=cdh3u2" is specified. coincidence?
> Here is the conf file:
> whirr.cluster-name=hadoop
> whirr.instance-templates=1 hadoop-namenode+hadoop-jobtracker+hadoop-datanode+hadoop-tasktracker
> whirr.env.repo=cdh3u2
> whirr.hadoop.install-function=install_cdh_hadoop
> whirr.hadoop.configure-function=configure_cdh_hadoop
> whirr.provider=aws-ec2
> whirr.identity=<deleted>
> whirr.credential=<deleted>
> whirr.hardware-id=t1.micro
> whirr.image-id=us-east-1/ami-baba68d3
> whirr.location-id=us-east-1

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira