[ 
https://issues.apache.org/jira/browse/IOTA-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556127#comment-15556127
 ] 

ASF GitHub Bot commented on IOTA-32:
------------------------------------

GitHub user barbaragomes opened a pull request:

    https://github.com/apache/incubator-iota/pull/21

    [IOTA-32] Fey - Define minimum number of actors when autoscaling

    New auto scaling configurations added to Fey:
    
    lowerBound: min number of actors
    upperBound: max number os actors
    backoffThreshold: Zero means that it will nevar scale down
    roundRobin: If true, then Router will use Round Robin distribution, 
otherwise it will use Smallest mailbox

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/barbaragomes/incubator-iota IOTA-32-RESIZE

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-iota/pull/21.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 #21
    
----
commit 76cf4616fa111ed5b1c9321984a0555a70edec0d
Author: Barbara Gomes <[email protected]>
Date:   2016-10-06T23:35:09Z

    [IOTA-32] Fey - Define minimum number of actors when autoscaling

----


> Fey - Define minimum number of actors when autoscaling
> ------------------------------------------------------
>
>                 Key: IOTA-32
>                 URL: https://issues.apache.org/jira/browse/IOTA-32
>             Project: Iota
>          Issue Type: New Feature
>            Reporter: Barbara Gomes
>            Assignee: Barbara Gomes
>            Priority: Minor
>
> Fey allows the user to specified only the up limit when he wants the actor to 
> autoscale. With this new feature the user will be able to specify the minimum 
> number of actors that should be running when auto scaling and as well as the 
> maximum number.
> For example:
> autoScale: 10
> minAutoScale: 5



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to