[
https://issues.jboss.org/browse/MODCLUSTER-449?page=com.atlassian.jira.pl...
]
Jean-Frederic Clere commented on MODCLUSTER-449:
------------------------------------------------
Actually any logic that can be done out of the native part is better.
It needs to be switchable from the node CLI and go by node so in tyhe CONFIG message...
The hack is to use the STATUS load value to reach what we want (AKA start with 0 and
increase by time depending on the load of node while we are increasing).
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)
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Critical
Fix For: 1.3.1.Beta3
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
(v6.3.11#6341)