[GitHub] brooklyn-server issue #923: DynamicCluster: resize to maxSize, before throwi...

[tbouron <gi...@git.apache.org>]

Github user tbouron commented on the issue:

    https://github.com/apache/brooklyn-server/pull/923
  
    @aledsage Code-wise, this looks fine.
    
    However, as I said in https://github.com/apache/brooklyn-server/pull/916#discussion_r158266008, I don't think this behaviour is the right thing to do. It will be hard to report back to the user what really happens. If one has `initialSize=5, maxSize=10` and resize by a delta of 10, how a user can know that it didn't resize to 15 because of the `maxSize` (the task won't tell this info explicitly) ? What highlight would be written if this was triggered by the `AutoScaller` policy?
    
    Fail fast is not as smart as this but at least, it will make sense to the user. That's why I was suggesting an effector's parameter which would override the behaviour to treat bounds as suggestions, not requirements. It would be a conscious decision from a user/policy rather than an arbitrary decision from our side.


---