brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aledsage <...@git.apache.org>
Subject [GitHub] brooklyn-server issue #487: Change default `machineCreateAttempts` to 3
Date Thu, 15 Dec 2016 15:59:18 GMT
Github user aledsage commented on the issue:

    https://github.com/apache/brooklyn-server/pull/487
  
    @bostko clouds will sometimes return a machine that is dead-on-arrival (DOA). It is impossible
to ssh to that machine, no matter how long you wait. Sometimes (less often) the VM being provisioned
in that cloud might fail, and will report a VM status of "starting" and then "error". It's
not as simple as the cloud API having failed to create the VM - a VM exists, but it's unusable.
    
    In those cases, jclouds will not retry. That's fine - we don't want jclouds to do the
retry logic, and instead to tell us about the failure. We'll get back the VM id that was provisioned,
and can then call jclouds to destroy the VM. Within Brooklyn, we can decide whether to retry.
    
    It varies how often these DOA VMs happen. From my experience, it used to be about 1 in
50 in AWS, but is even less common now. In some other clouds, it's more common.
    
    This param is particularly important if provisioning bigger clusters, or many apps, as
obviously it's more likely to happen if provisioning many things.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message