[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-449) Implement ramp-up when starting new nodes

Radoslav Husar (JIRA) issues at jboss.org
Fri Aug 25 12:06:00 EDT 2017


    [ https://issues.jboss.org/browse/MODCLUSTER-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454265#comment-13454265 ] 

Radoslav Husar commented on MODCLUSTER-449:
-------------------------------------------

The configuration option is {{initialLoad="50"}} to start with load of 50 which will decay acording to decay configuration.

> Implement ramp-up when starting new nodes
> -----------------------------------------
>
>                 Key: MODCLUSTER-449
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-449
>             Project: mod_cluster
>          Issue Type: Feature Request
>          Components: Core & Container Integration (Java)
>    Affects Versions: 1.2.0.Final, 1.3.0.Final
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>            Priority: Blocker
>             Fix For: 1.4.0.Alpha1, 2.0.0.Alpha1
>
>         Attachments: httpdRamp-up.jpg, undertowRamp-up.jpg
>
>
> IIUC this has been a problem since inception. The problem is that the initial load stays in effect for performing load-balancing decisions until a new stat interval kicks in. 
> This effect is mitigated by load decay over time, but for the time a new node joins in, it can get overloaded upon startup.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the mod_cluster-issues mailing list