brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-212) Auto-scaling in finite BYON cluster keeps adding on-fire entities
Date Wed, 13 Jan 2016 11:51:40 GMT


ASF GitHub Bot commented on BROOKLYN-212:

Github user johnmccabe commented on the pull request:
    You can still produce onfire member entities as follows:
    - Use  [this]( catalog in place
of the default (`./bin/brooklyn launch --catalogInitial file:///path/to/bom`)
    - Deploy template 4 from above, setting the `maxPoolSize:` to exceed the number of nodes
in your byon pool
    - Navigate to the balancer endpoint and repeatedly hit refresh in your browser, you should
observe the cluster quickly scaling up before on fire members start appearing.

> Auto-scaling in finite BYON cluster keeps adding on-fire entities
> -----------------------------------------------------------------
>                 Key: BROOKLYN-212
>                 URL:
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Aled Sage
> When using a BYON location of a limited size (e.g. four vagrant VMs), if an auto-scaler
policy tries to resize above this number of VMs then it goes badly wrong!
> Auto-scaling causes a new entity to be added to the cluster, but it fails to start because
the {{location.obtain()}} call fails. That entity is left in quarantine, on-fire.
> The auto-scaler will then try again: another new entity is added, but this also fails.
This repeats, adding more and more entities.

This message was sent by Atlassian JIRA

View raw message