April 2019 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-471) Mod_cluster performance on httpd 2.4

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-471?page=com.atlassian.jira.pl... ] Jean-Frederic Clere closed MODCLUSTER-471. ------------------------------------------ Resolution: Out of Date > Mod_cluster performance on httpd 2.4 > ------------------------------------ > > Key: MODCLUSTER-471 > URL: https://issues.jboss.org/browse/MODCLUSTER-471 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.1.Final > Reporter: Coty Sutherland > Assignee: Jean-Frederic Clere > Priority: Major > Attachments: reproducer.tar.gz > > > When using mod_cluster with httpd 2.4 (specifically with the JWS 3.0.1 product family) in front of EAP 6.3 there is a noticeable performance decrease in requests being serviced from httpd. This seemingly is resolved by using the latest (at presently 1.3.2.Alpha), but research hasn't pointed to a specific fix there, so I'm opening this. We were thinking that it had something to do with module loading order, but haven't been able to confirm that. > One more important note is that the user is fronting about 250+ (up to 290) JBoss instances behind a single balancer. I'm attaching the reproduction script that the user provided. It needs a receiver (a mod_cluster node running on localhost port 8009) and an httpd balancer. Then you can run the create script to create the nodes and the update script to update them using netcat to prevent the need for 250 real instances. It is a bit hacky, but it could save you some resources. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-448) mod_cluster crashes apache thread if multiple nodes report the same AJP connect string

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-448?page=com.atlassian.jira.pl... ] Jean-Frederic Clere closed MODCLUSTER-448. ------------------------------------------ Resolution: Won't Fix as 2.4.x is the supported version we won't investigate that issue any more. > mod_cluster crashes apache thread if multiple nodes report the same AJP connect string > -------------------------------------------------------------------------------------- > > Key: MODCLUSTER-448 > URL: https://issues.jboss.org/browse/MODCLUSTER-448 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.2.6.Final > Reporter: Michal Karm > Assignee: Michal Karm > Priority: Major > > Reported on behalf of [Toby Murray|https://github.com/ToeBee]: > Tracking issue #[138|https://github.com/modcluster/mod_cluster/issues/138] > Let's carry on with any discussion here, on JIRA... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-470) Documentation states stickySessionForce defaults to true in modcluster subsystem and defaults to false in Proxy Configuration

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-470?page=com.atlassian.jira.pl... ] Jean-Frederic Clere resolved MODCLUSTER-470. -------------------------------------------- Resolution: Done fixed in https://github.com/modcluster/docs.modcluster.io > Documentation states stickySessionForce defaults to true in modcluster subsystem and defaults to false in Proxy Configuration > ----------------------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-470 > URL: https://issues.jboss.org/browse/MODCLUSTER-470 > Project: mod_cluster > Issue Type: Bug > Components: Documentation & Demos > Affects Versions: 1.3.0.Final > Reporter: Robert Bost > Assignee: Jean-Frederic Clere > Priority: Major > > http://docs.jboss.org/mod_cluster/1.3.0/html_single/ shows conflicting explanations of stickySessionForce defaults -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-507) Worker22 on RHEL-7 [mod_cluster segfaults]

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-507?page=com.atlassian.jira.pl... ] Jean-Frederic Clere closed MODCLUSTER-507. ------------------------------------------ Fix Version/s: 1.3.2.Final (was: 1.2.14.Final) Resolution: Done > Worker22 on RHEL-7 [mod_cluster segfaults] > ------------------------------------------ > > Key: MODCLUSTER-507 > URL: https://issues.jboss.org/browse/MODCLUSTER-507 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.9.Final > Environment: mod_cluster-1.3.2 *IS NOT* affected any more > Reporter: Michal Karm > Assignee: Jean-Frederic Clere > Priority: Major > Fix For: 1.3.2.Final > > > Long term (days) running on httpd 2.2.26, with *worker* MPM on RHEL 7 x86_64, random segfaults in mod_manager. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-508) &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-508?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-508: ------------------------------------------- Fix Version/s: 2.0.0.Alpha2 > &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful > ------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-508 > URL: https://issues.jboss.org/browse/MODCLUSTER-508 > Project: mod_cluster > Issue Type: Enhancement > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.13.Final > Reporter: Michal Karm > Assignee: Jean-Frederic Clere > Priority: Trivial > Fix For: 2.0.0.Alpha2 > > > While we compare balancers URL char by char, we start at index 11, because > the default beginning: {{balancer://}} is always there. It would be nice to change 11 to a named constant so as it is clear why it's 11 without debugger :) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-508) &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-508?page=com.atlassian.jira.pl... ] Jean-Frederic Clere reassigned MODCLUSTER-508: ---------------------------------------------- Assignee: Jean-Frederic Clere (was: Michal Karm) > &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful > ------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-508 > URL: https://issues.jboss.org/browse/MODCLUSTER-508 > Project: mod_cluster > Issue Type: Enhancement > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.13.Final > Reporter: Michal Karm > Assignee: Jean-Frederic Clere > Priority: Trivial > Fix For: 2.0.0.Alpha2 > > > While we compare balancers URL char by char, we start at index 11, because > the default beginning: {{balancer://}} is always there. It would be nice to change 11 to a named constant so as it is clear why it's 11 without debugger :) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-508) &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful

by Jean-Frederic Clere (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-508?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-508: ------------------------------------------------ #define BALANCER_PREFIX "balancer://" im mod_proxy https://github.com/apache/httpd/blob/2.4.x/modules/proxy/mod_proxy.h#L94 > &balancer->name[11], because of default: balancer://mycluster: Change magic number 11 to something meaningful > ------------------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-508 > URL: https://issues.jboss.org/browse/MODCLUSTER-508 > Project: mod_cluster > Issue Type: Enhancement > Components: Native (httpd modules) > Affects Versions: 1.3.2.Final, 1.2.13.Final > Reporter: Michal Karm > Assignee: Michal Karm > Priority: Trivial > > While we compare balancers URL char by char, we start at index 11, because > the default beginning: {{balancer://}} is always there. It would be nice to change 11 to a named constant so as it is clear why it's 11 without debugger :) -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-567) Deprecate excludedContexts

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-567?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-567: -------------------------------------- Affects Version/s: 1.4.0.Final > Deprecate excludedContexts > -------------------------- > > Key: MODCLUSTER-567 > URL: https://issues.jboss.org/browse/MODCLUSTER-567 > Project: mod_cluster > Issue Type: Task > Components: Core & Container Integration (Java) > Affects Versions: 1.3.6.CR1, 1.4.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Priority: Major > Fix For: 2.0.0.Alpha1 > > > "Excluded contexts" is an artifact of poor deployment encapsulation. All contexts within a given engine should be registered with the load balancer. If there are application that should not be load balanced, then they should be deployed to a different engine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-591) MemManagerFile should not default to server_root + "/logs"

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-591?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-591: ------------------------------------------- Just for the record, the original fix for this was rejected https://github.com/modcluster/mod_proxy_cluster/pull/13 > MemManagerFile should not default to server_root + "/logs" > ---------------------------------------------------------- > > Key: MODCLUSTER-591 > URL: https://issues.jboss.org/browse/MODCLUSTER-591 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.6.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Priority: Major > Fix For: 2.0.0.Alpha1 > > > It seems the server_root + "/cache" is a better default for the current set of mod_cluster distributions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-591) MemManagerFile should not default to server_root + "/logs"

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/MODCLUSTER-591?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-591: ----------------------------------------- Assignee: Jean-Frederic Clere > MemManagerFile should not default to server_root + "/logs" > ---------------------------------------------------------- > > Key: MODCLUSTER-591 > URL: https://issues.jboss.org/browse/MODCLUSTER-591 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.3.6.Final > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Priority: Major > Fix For: 2.0.0.Alpha1 > > > It seems the server_root + "/cache" is a better default for the current set of mod_cluster distributions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues April 2019