whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrei Savu (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WHIRR-410) Review automatic image selection
Date Tue, 08 Nov 2011 22:07:51 GMT

     [ https://issues.apache.org/jira/browse/WHIRR-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Andrei Savu updated WHIRR-410:

    Attachment: jclouds-ssh.log

This is stil a problem when using t1.micro with a 32bit OS but I think I've found the root
cause: we are flooding the ssh server with too many status update requests for the init script
(executed on bootstrap) - check the attached log file. 

Is there a way to rate limit this? (how often jclouds check if a script finished executing)
> Review automatic image selection
> --------------------------------
>                 Key: WHIRR-410
>                 URL: https://issues.apache.org/jira/browse/WHIRR-410
>             Project: Whirr
>          Issue Type: Bug
>            Reporter: Andrei Savu
>             Fix For: 0.7.0
>         Attachments: WHIRR-410.patch, jclouds-ssh.log
> While I was testing WHIRR-400 I have noticed that the ZooKeeper integration tests are
failing on aws-ec2 with the automatically selected AMI but they are working as expected with
the Amazon Linux AMI. The tests are also working as expected on cloudservers-us. This makes
me think the failure is not related to our code changes and we should look for an external
factor as the root cause. 
> As part of this issue we should think about how to improve the automatic AMI selection
mechanism in order to make it more robust and less likely to fail due to AMI upgrades and
other external changes. 

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


View raw message