[JBoss JIRA] (MODCLUSTER-612) Test DefaultMCMPRequestFactoryTestCase#createConfigRequest fails on Windows OS with other than lowercase hostname
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-612?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-612:
--------------------------------------
Fix Version/s: 2.0.0.Alpha1
1.4.0.Alpha1
> Test DefaultMCMPRequestFactoryTestCase#createConfigRequest fails on Windows OS with other than lowercase hostname
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-612
> URL: https://issues.jboss.org/browse/MODCLUSTER-612
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Affects Versions: 1.2.13.Final, 1.3.7.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 2.0.0.Alpha1, 1.4.0.Alpha1
>
>
> {code}
> [ERROR] createConfigRequest(org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase) Time elapsed: 0 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
> at org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase.createConfigRequest(DefaultMCMPRequestFactoryTestCase.java:210)
> [INFO] Running org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
> [INFO] Running org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s - in org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
> [INFO] Running org.jboss.modcluster.UtilsTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.UtilsTestCase
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] DefaultMCMPRequestFactoryTestCase.createConfigRequest:210 expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
> [INFO]
> [ERROR] Tests run: 50, Failures: 1, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-612) Test DefaultMCMPRequestFactoryTestCase#createConfigRequest fails on Windows OS with other than lowercase hostname
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-612?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-612:
--------------------------------------
Summary: Test DefaultMCMPRequestFactoryTestCase#createConfigRequest fails on Windows OS with other than lowercase hostname (was: DefaultMCMPRequestFactoryTestCase.createConfigRequest fails on Windows OS with other than lowercase hostname)
> Test DefaultMCMPRequestFactoryTestCase#createConfigRequest fails on Windows OS with other than lowercase hostname
> -----------------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-612
> URL: https://issues.jboss.org/browse/MODCLUSTER-612
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> {code}
> [ERROR] createConfigRequest(org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase) Time elapsed: 0 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
> at org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase.createConfigRequest(DefaultMCMPRequestFactoryTestCase.java:210)
> [INFO] Running org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
> [INFO] Running org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s - in org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
> [INFO] Running org.jboss.modcluster.UtilsTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.UtilsTestCase
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] DefaultMCMPRequestFactoryTestCase.createConfigRequest:210 expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
> [INFO]
> [ERROR] Tests run: 50, Failures: 1, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-612) DefaultMCMPRequestFactoryTestCase.createConfigRequest fails on Windows OS with other than lowercase hostname
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-612?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-612:
--------------------------------------
Description:
{code}
[ERROR] createConfigRequest(org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase) Time elapsed: 0 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
at org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase.createConfigRequest(DefaultMCMPRequestFactoryTestCase.java:210)
[INFO] Running org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Running org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s - in org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Running org.jboss.modcluster.UtilsTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.UtilsTestCase
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] DefaultMCMPRequestFactoryTestCase.createConfigRequest:210 expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
[INFO]
[ERROR] Tests run: 50, Failures: 1, Errors: 0, Skipped: 0
{code}
was:
{noformat}
[ERROR] createConfigRequest(org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase) Time elapsed: 0 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
at org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase.createConfigRequest(DefaultMCMPRequestFactoryTestCase.java:210)
[INFO] Running org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Running org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s - in org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Running org.jboss.modcluster.UtilsTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.UtilsTestCase
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] DefaultMCMPRequestFactoryTestCase.createConfigRequest:210 expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
[INFO]
[ERROR] Tests run: 50, Failures: 1, Errors: 0, Skipped: 0
{noformat}
> DefaultMCMPRequestFactoryTestCase.createConfigRequest fails on Windows OS with other than lowercase hostname
> ------------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-612
> URL: https://issues.jboss.org/browse/MODCLUSTER-612
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> {code}
> [ERROR] createConfigRequest(org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase) Time elapsed: 0 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
> at org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase.createConfigRequest(DefaultMCMPRequestFactoryTestCase.java:210)
> [INFO] Running org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
> [INFO] Running org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s - in org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
> [INFO] Running org.jboss.modcluster.UtilsTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.UtilsTestCase
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] DefaultMCMPRequestFactoryTestCase.createConfigRequest:210 expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
> [INFO]
> [ERROR] Tests run: 50, Failures: 1, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-612) DefaultMCMPRequestFactoryTestCase.createConfigRequest fails on Windows OS with other than lowercase hostname
by Radoslav Husar (JIRA)
Radoslav Husar created MODCLUSTER-612:
-----------------------------------------
Summary: DefaultMCMPRequestFactoryTestCase.createConfigRequest fails on Windows OS with other than lowercase hostname
Key: MODCLUSTER-612
URL: https://issues.jboss.org/browse/MODCLUSTER-612
Project: mod_cluster
Issue Type: Bug
Components: Core & Container Integration (Java)
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Minor
[ERROR] createConfigRequest(org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase) Time elapsed: 0 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
at org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase.createConfigRequest(DefaultMCMPRequestFactoryTestCase.java:210)
[INFO] Running org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Running org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s - in org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Running org.jboss.modcluster.UtilsTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.UtilsTestCase
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] DefaultMCMPRequestFactoryTestCase.createConfigRequest:210 expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
[INFO]
[ERROR] Tests run: 50, Failures: 1, Errors: 0, Skipped: 0
[INFO]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-612) DefaultMCMPRequestFactoryTestCase.createConfigRequest fails on Windows OS with other than lowercase hostname
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-612?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-612:
--------------------------------------
Description:
{noformat}
[ERROR] createConfigRequest(org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase) Time elapsed: 0 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
at org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase.createConfigRequest(DefaultMCMPRequestFactoryTestCase.java:210)
[INFO] Running org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Running org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s - in org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Running org.jboss.modcluster.UtilsTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.UtilsTestCase
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] DefaultMCMPRequestFactoryTestCase.createConfigRequest:210 expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
[INFO]
[ERROR] Tests run: 50, Failures: 1, Errors: 0, Skipped: 0
{noformat}
was:
[ERROR] createConfigRequest(org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase) Time elapsed: 0 s <<< FAILURE!
org.junit.ComparisonFailure: expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
at org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase.createConfigRequest(DefaultMCMPRequestFactoryTestCase.java:210)
[INFO] Running org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
[INFO] Running org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s - in org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
[INFO] Running org.jboss.modcluster.UtilsTestCase
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.UtilsTestCase
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] DefaultMCMPRequestFactoryTestCase.createConfigRequest:210 expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
[INFO]
[ERROR] Tests run: 50, Failures: 1, Errors: 0, Skipped: 0
[INFO]
> DefaultMCMPRequestFactoryTestCase.createConfigRequest fails on Windows OS with other than lowercase hostname
> ------------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-612
> URL: https://issues.jboss.org/browse/MODCLUSTER-612
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> {noformat}
> [ERROR] createConfigRequest(org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase) Time elapsed: 0 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
> at org.jboss.modcluster.mcmp.DefaultMCMPRequestFactoryTestCase.createConfigRequest(DefaultMCMPRequestFactoryTestCase.java:210)
> [INFO] Running org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.mcmp.DefaultMCMPResponseParserTestCase
> [INFO] Running org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
> [INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s - in org.jboss.modcluster.mcmp.ResetRequestSourceTestCase
> [INFO] Running org.jboss.modcluster.UtilsTestCase
> [INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in org.jboss.modcluster.UtilsTestCase
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Failures:
> [ERROR] DefaultMCMPRequestFactoryTestCase.createConfigRequest:210 expected:<[DESKTOP-614P6ER]> but was:<[desktop-614p6er]>
> [INFO]
> [ERROR] Tests run: 50, Failures: 1, Errors: 0, Skipped: 0
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-449) Implement ramp-up when starting new nodes
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-449?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-449:
--------------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/modcluster/mod_cluster/pull/284
> 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: 2.0.0.Alpha1, 1.4.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)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-449) Implement ramp-up when starting new nodes
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-449?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-449:
--------------------------------------
Priority: Blocker (was: Critical)
> 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: 2.0.0.Alpha1, 1.4.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)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-449) Implement ramp-up when starting new nodes
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-449?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-449:
--------------------------------------
Fix Version/s: 1.4.0.Alpha1
> 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: Critical
> Fix For: 2.0.0.Alpha1, 1.4.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)
7 years, 4 months
[JBoss JIRA] (MODCLUSTER-449) Implement ramp-up when starting new nodes
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-449?page=com.atlassian.jira.pl... ]
Work on MODCLUSTER-449 started by Radoslav Husar.
-------------------------------------------------
> 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: Critical
> Fix For: 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)
7 years, 4 months