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 Thu, 14 Jan 2016 13:24:39 GMT


ASF GitHub Bot commented on BROOKLYN-212:

Github user johnmccabe commented on the pull request:
    @aledsage that looks good with no on-fire entities observed !!
    Observed the following with `maxPoolSize` to 5 and only 3 nodes available in the pool:

    - completed resize task from 1-3
    - completed resize task from 3-5
      - which has a failed child task `starting 2 nodes (parallel)`.
    org.apache.brooklyn.util.exceptions.CompoundRuntimeException: 2 of 2 parallel child tasks
failed, 2 errors including: org.apache.brooklyn.util.exceptions.PropagatedRuntimeException:
Error invoking start at BasicApplicationImpl{id=kYMCHlUI}: org.apache.brooklyn.util.exceptions.PropagatedRuntimeException:
org.apache.brooklyn.util.exceptions.PropagatedRuntimeException: org.apache.brooklyn.util.exceptions.PropagatedRuntimeException:
Error invoking start at VanillaSoftwareProcessImpl{id=NBfPZEAU}: org.apache.brooklyn.util.exceptions.PropagatedRuntimeException:
org.apache.brooklyn.api.location.NoMachinesAvailableException: No machines available in FixedListMachineProvisioningLocation{id=l6QbvlPY,
    Also observe the suppressing warning in logs:
    2016-01-14 13:15:56,504 WARN  AutoScalerPolicy(Auto-scaler) failed to resize DynamicClusterImpl{id=AIvl1Kpr}
due to insufficient capacity; setting high-water mark to 3, and will not attempt to resize
above that level again

> 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