November 2013 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-372) Number of registered contexts negatively affects mod_cluster performance

by Michal Babacek (JIRA)

Michal Babacek created MODCLUSTER-372: ----------------------------------------- Summary: Number of registered contexts negatively affects mod_cluster performance Key: MODCLUSTER-372 URL: https://issues.jboss.org/browse/MODCLUSTER-372 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.6.Final, 1.2.4.Final Environment: RHEL6, other platforms are to be confirmed. Reporter: Michal Babacek Assignee: Michal Babacek Detailed description and statistics are coming soon... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-369) httpd should remove lost node/worker

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-369?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-369: ------------------------------------------------ According to the trace the end user shouldn't notice the problem (well the answer is delayed for ping seconds due to the retry. +++ [jfclere@jfcpc TMP]$ grep "(attempt" httpd-error.log | grep -v "0)" Nov 11 08:33:25 httpd[12006]: [debug] mod_proxy.c(1028): Running scheme balancer handler (attempt 1) Nov 11 08:33:30 httpd[12006]: [debug] mod_proxy.c(1028): Running scheme balancer handler (attempt 1) Nov 11 08:33:42 httpd[12006]: [debug] mod_proxy.c(1028): Running scheme balancer handler (attempt 1) +++ > httpd should remove lost node/worker > ------------------------------------ > > Key: MODCLUSTER-369 > URL: https://issues.jboss.org/browse/MODCLUSTER-369 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.0.Final, 1.2.6.Final > Environment: httpd 2.2.24+tomcat 7.0.37 > Reporter: Stefano Nichele > Assignee: Jean-Frederic Clere > Priority: Critical > Attachments: httpd-error.log > > > supposing this env running on amazon: > - one virtual machine running HTTPD (let's call it FE) > - two virtual machines running tomcat (let's call them NODE01 and NODE02) > If NODE02 virtual machine dies or crash for any reason, HTTPD still report it in mod_cluster-manager sometime view with status ok and sometime with status notok. > Moreover some requests are still sent to the dead node. > Please note i replicated this behavior just closing netwrok traffic using iptables on NODE02: > iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -m tcp --dport 6666 -j DROP > iptables -A INPUT -m state --state NEW,ESTABLISHED -p tcp --dport 8009 -j DROP > In this way tomcat instance is not able to send its status and HTTPD is not able to sends traffic on port 8009. > In my opinion two issues here: > 1. if HTTPD doesn't recevice any STATUS from a worker, the worker mustb e at least marked as NOTOK > 2. it seems that HTTPD considers the worker available during its retry policy and this causes that some requests are still forwarded to that node and it causes the worker appears as flapping. > Original threads:https://community.jboss.org/thread/234235 > Marking this is as critical since amazon is one of the main player in virtualization and if on a production environment an instance disappears (it can happen in any moment) the whole production environemnet is affected (since some requests are still send to the dead node). > In attahcment httpd error log file produced using modcluster 1.2.6. > at 08:32:30 HTTPD has been restarted (with two wrokers OK) > at 08:33:10 instance NODE02 (IP: 10.2.2.2) disappears > at 08:33:25 NODE2 is marked as NOTOK > at 08:33:32 NODE02 is marked as OK > at 08:33:41 NODE2 is marked as NOTOK > ...and so on... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-369) httpd should remove lost node/worker

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-369?page=com.atlassian.jira.pl... ] Jean-Frederic Clere updated MODCLUSTER-369: ------------------------------------------- Priority: Major (was: Critical) > httpd should remove lost node/worker > ------------------------------------ > > Key: MODCLUSTER-369 > URL: https://issues.jboss.org/browse/MODCLUSTER-369 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.0.Final, 1.2.6.Final > Environment: httpd 2.2.24+tomcat 7.0.37 > Reporter: Stefano Nichele > Assignee: Jean-Frederic Clere > Attachments: httpd-error.log > > > supposing this env running on amazon: > - one virtual machine running HTTPD (let's call it FE) > - two virtual machines running tomcat (let's call them NODE01 and NODE02) > If NODE02 virtual machine dies or crash for any reason, HTTPD still report it in mod_cluster-manager sometime view with status ok and sometime with status notok. > Moreover some requests are still sent to the dead node. > Please note i replicated this behavior just closing netwrok traffic using iptables on NODE02: > iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -m tcp --dport 6666 -j DROP > iptables -A INPUT -m state --state NEW,ESTABLISHED -p tcp --dport 8009 -j DROP > In this way tomcat instance is not able to send its status and HTTPD is not able to sends traffic on port 8009. > In my opinion two issues here: > 1. if HTTPD doesn't recevice any STATUS from a worker, the worker mustb e at least marked as NOTOK > 2. it seems that HTTPD considers the worker available during its retry policy and this causes that some requests are still forwarded to that node and it causes the worker appears as flapping. > Original threads:https://community.jboss.org/thread/234235 > Marking this is as critical since amazon is one of the main player in virtualization and if on a production environment an instance disappears (it can happen in any moment) the whole production environemnet is affected (since some requests are still send to the dead node). > In attahcment httpd error log file produced using modcluster 1.2.6. > at 08:32:30 HTTPD has been restarted (with two wrokers OK) > at 08:33:10 instance NODE02 (IP: 10.2.2.2) disappears > at 08:33:25 NODE2 is marked as NOTOK > at 08:33:32 NODE02 is marked as OK > at 08:33:41 NODE2 is marked as NOTOK > ...and so on... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-371) Automated GitHub pull request testing: build Native part and its tests

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-371: ----------------------------------------- Summary: Automated GitHub pull request testing: build Native part and its tests Key: MODCLUSTER-371 URL: https://issues.jboss.org/browse/MODCLUSTER-371 Project: mod_cluster Issue Type: Sub-task Affects Versions: 1.3.0.Alpha1 Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 1.3.0.Alpha2 Also build native part. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-370) Automated GitHub pull request testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-370?page=com.atlassian.jira.pl... ] Radoslav Husar resolved MODCLUSTER-370. --------------------------------------- Resolution: Done Done, however, currently only builds and tests via maven targets -- so only the Java part. More installation is needed to build the native part. > Automated GitHub pull request testing > ------------------------------------- > > Key: MODCLUSTER-370 > URL: https://issues.jboss.org/browse/MODCLUSTER-370 > Project: mod_cluster > Issue Type: Task > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.0.Alpha2 > > > Same as we have for other projects (e.g. WildFly). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-370) Automated GitHub pull request testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-370?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-370: ------------------------------------------- Example: https://github.com/modcluster/mod_cluster/pull/32 > Automated GitHub pull request testing > ------------------------------------- > > Key: MODCLUSTER-370 > URL: https://issues.jboss.org/browse/MODCLUSTER-370 > Project: mod_cluster > Issue Type: Task > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 1.3.0.Alpha2 > > > Same as we have for other projects (e.g. WildFly). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-370) Automated GitHub pull request testing

by Radoslav Husar (JIRA)

Radoslav Husar created MODCLUSTER-370: ----------------------------------------- Summary: Automated GitHub pull request testing Key: MODCLUSTER-370 URL: https://issues.jboss.org/browse/MODCLUSTER-370 Project: mod_cluster Issue Type: Task Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 1.3.0.Alpha2 Same as we have for other projects (e.g. WildFly). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-369) httpd should remove lost node/worker

by Stefano Nichele (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-369?page=com.atlassian.jira.pl... ] Stefano Nichele updated MODCLUSTER-369: --------------------------------------- Attachment: httpd-error.log httpd error log > httpd should remove lost node/worker > ------------------------------------ > > Key: MODCLUSTER-369 > URL: https://issues.jboss.org/browse/MODCLUSTER-369 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.0.Final, 1.2.6.Final > Environment: httpd 2.2.24+tomcat 7.0.37 > Reporter: Stefano Nichele > Assignee: Jean-Frederic Clere > Priority: Critical > Attachments: httpd-error.log > > > supposing this env running on amazon: > - one virtual machine running HTTPD (let's call it FE) > - two virtual machines running tomcat (let's call them NODE01 and NODE02) > If NODE02 virtual machine dies or crash for any reason, HTTPD still report it in mod_cluster-manager sometime view with status ok and sometime with status notok. > Moreover some requests are still sent to the dead node. > Please note i replicated this behavior just closing netwrok traffic using iptables on NODE02: > iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -m tcp --dport 6666 -j DROP > iptables -A INPUT -m state --state NEW,ESTABLISHED -p tcp --dport 8009 -j DROP > In this way tomcat instance is not able to send its status and HTTPD is not able to sends traffic on port 8009. > In my opinion two issues here: > 1. if HTTPD doesn't recevice any STATUS from a worker, the worker mustb e at least marked as NOTOK > 2. it seems that HTTPD considers the worker available during its retry policy and this causes that some requests are still forwarded to that node and it causes the worker appears as flapping. > Original threads:https://community.jboss.org/thread/234235 > Marking this is as critical since amazon is one of the main player in virtualization and if on a production environment an instance disappears (it can happen in any moment) the whole production environemnet is affected (since some requests are still send to the dead node). > In attahcment httpd error log file produced using modcluster 1.2.6. > at 08:32:30 HTTPD has been restarted (with two wrokers OK) > at 08:33:10 instance NODE02 (IP: 10.2.2.2) disappears > at 08:33:25 NODE2 is marked as NOTOK > at 08:33:32 NODE02 is marked as OK > at 08:33:41 NODE2 is marked as NOTOK > ...and so on... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-369) httpd should remove lost node/worker

by Stefano Nichele (JIRA)

Stefano Nichele created MODCLUSTER-369: ------------------------------------------ Summary: httpd should remove lost node/worker Key: MODCLUSTER-369 URL: https://issues.jboss.org/browse/MODCLUSTER-369 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.6.Final, 1.2.0.Final Environment: httpd 2.2.24+tomcat 7.0.37 Reporter: Stefano Nichele Assignee: Jean-Frederic Clere Priority: Critical supposing this env running on amazon: - one virtual machine running HTTPD (let's call it FE) - two virtual machines running tomcat (let's call them NODE01 and NODE02) If NODE02 virtual machine dies or crash for any reason, HTTPD still report it in mod_cluster-manager sometime view with status ok and sometime with status notok. Moreover some requests are still sent to the dead node. Please note i replicated this behavior just closing netwrok traffic using iptables on NODE02: iptables -A OUTPUT -p tcp -m state --state NEW,ESTABLISHED -m tcp --dport 6666 -j DROP iptables -A INPUT -m state --state NEW,ESTABLISHED -p tcp --dport 8009 -j DROP In this way tomcat instance is not able to send its status and HTTPD is not able to sends traffic on port 8009. In my opinion two issues here: 1. if HTTPD doesn't recevice any STATUS from a worker, the worker mustb e at least marked as NOTOK 2. it seems that HTTPD considers the worker available during its retry policy and this causes that some requests are still forwarded to that node and it causes the worker appears as flapping. Original threads:https://community.jboss.org/thread/234235 Marking this is as critical since amazon is one of the main player in virtualization and if on a production environment an instance disappears (it can happen in any moment) the whole production environemnet is affected (since some requests are still send to the dead node). In attahcment httpd error log file produced using modcluster 1.2.6. at 08:32:30 HTTPD has been restarted (with two wrokers OK) at 08:33:10 instance NODE02 (IP: 10.2.2.2) disappears at 08:33:25 NODE2 is marked as NOTOK at 08:33:32 NODE02 is marked as OK at 08:33:41 NODE2 is marked as NOTOK ...and so on... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-365) Reset MCMPs are sent to all available proxies

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-365?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated MODCLUSTER-365: ----------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1026433, https://bugzilla.redhat.com/show_bug.cgi?id=1028376 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1026433) > Reset MCMPs are sent to all available proxies > --------------------------------------------- > > Key: MODCLUSTER-365 > URL: https://issues.jboss.org/browse/MODCLUSTER-365 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.6.Final > Environment: -JBoss Enterprise Application Platform (EAP) 6.1.1 > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > Consider a JBoss server with multiple httpd servers defined in its proxy-list. If one of those httpd servers goes down and then comes back up, then reset MCMPs (CONFIG, ENABLE-APP) would be sent to the restarted httpd proxy but needlessly to all other proxies as well. This is because DefaultMCMPHandler.status just calls sendRequests, which will send to all proxies by design. > This has negative implications if auto-enable-contexts is set to false and can break desired behavior. Reproducer steps detail the issue introduced in that scenario. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues November 2013