GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/923
DynamicCluster: resize to maxSize, before throwing InsufficientCapacity
Building on PR #916 and the conversation in
https://github.com/apache/brooklyn-server/pull/916#discussion_r157902790, this
changes the behaviour of resize so that it will grow to the maxSize.
For example, imaging the extreme case where we have `initialSize=1,
maxSize=10`, and an auto-scaler policy decides that the cluster should be
resized to 11. Instead of throwing an exception, the behaviour now will be that
the first call to `resize(11)` will cause us to resize to the max of 10
(logging a warning). A subsequent call to `resize(11)` by the policy will throw
the `InsufficientCapacityException`.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server pr916-grow-to-maxSize
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/923.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #923
----
commit 72b0bf1e38330806f5168fb613c3ae75c8307077
Author: Aled Sage <aled.sage@...>
Date: 2017-12-21T15:21:22Z
DynamicCluster: resize to maxSize, before throwing InsufficientCapacity
----
---
