You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Doug Daniels (JIRA)" <ji...@apache.org> on 2012/05/11 17:44:50 UTC
[jira] [Updated] (WHIRR-590) ssh port timeout fails the whole
cluster
[ https://issues.apache.org/jira/browse/WHIRR-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Daniels updated WHIRR-590:
-------------------------------
Attachment: WHIRR-590.patch
> ssh port timeout fails the whole cluster
> ----------------------------------------
>
> Key: WHIRR-590
> URL: https://issues.apache.org/jira/browse/WHIRR-590
> Project: Whirr
> Issue Type: Bug
> Affects Versions: 0.7.1
> Reporter: Doug Daniels
> Attachments: WHIRR-590.patch
>
>
> If the ssh port does not open before the jclouds.compute.timeout.port-open timeout, the whole cluster fails to launch rather than starting a replacement for the failed node and continuing provisioning. You can simulate this by setting your jclouds.compute.timeout.port-open to something very small, such as:
> jclouds.compute.timeout.port-open=5
> I believe that the failure happens because the node winds up both the successfulNodes and the lostNodes reported by the RunNodesException. I filed a bug for this in jclouds: https://code.google.com/p/jclouds/issues/detail?id=923
--
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