April 2018 - mod_cluster-issues - Jboss List Archives

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

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-369?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-369: -------------------------------------- Component/s: Native (httpd modules) > httpd should remove lost node/worker > ------------------------------------ > > Key: MODCLUSTER-369 > URL: https://issues.jboss.org/browse/MODCLUSTER-369 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > 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: Minor > 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 was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-573) Excluded contexts on http://modcluster.io/documentation/

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-573?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-573: ----------------------------------------- Assignee: Radoslav Husar (was: Michal Karm Babacek) > Excluded contexts on http://modcluster.io/documentation/ > -------------------------------------------------------- > > Key: MODCLUSTER-573 > URL: https://issues.jboss.org/browse/MODCLUSTER-573 > Project: mod_cluster > Issue Type: Bug > Components: Documentation & Demos > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > > [~bsikora] reported: > {quote} > http://modcluster.io/documentation/ > Excluded contexts > > Tomcat attributeAS7/Wildfly attributeWildfly DefaultTomcat/AS7 Default > > LocationScope > > excludedContexts excluded-contexts *None* ROOT, admin-console, invoker, > > bossws, jmx-console, juddi, web-console Worker Worker > > > > List of contexts to exclude from httpd registration, of the form: *host1*: > > *context1*,*host2*:*context2*,*host3*:*context3* If no host is indicated, > > it is assumed to be the default host of the server (e.g. localhost). “ROOT” > > indicates the root context. Using the default configuration, this property > > can by manipulated via the jboss.mod_cluster.excludedContexts system > > property. > > > IMHO conflict with JBEAP-5058 > Cheers, > Bogdan Sikora > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 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: (was: Radoslav Husar) > 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 > 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.5.0#75005)

6 years, 2 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 updated MODCLUSTER-591: -------------------------------------- Git Pull Request: (was: 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 > 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.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-573) Excluded contexts on http://modcluster.io/documentation/

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-573?page=com.atlassian.jira.pl... ] Work on MODCLUSTER-573 started by Radoslav Husar. ------------------------------------------------- > Excluded contexts on http://modcluster.io/documentation/ > -------------------------------------------------------- > > Key: MODCLUSTER-573 > URL: https://issues.jboss.org/browse/MODCLUSTER-573 > Project: mod_cluster > Issue Type: Bug > Components: Documentation & Demos > Reporter: Michal Karm Babacek > Assignee: Radoslav Husar > > [~bsikora] reported: > {quote} > http://modcluster.io/documentation/ > Excluded contexts > > Tomcat attributeAS7/Wildfly attributeWildfly DefaultTomcat/AS7 Default > > LocationScope > > excludedContexts excluded-contexts *None* ROOT, admin-console, invoker, > > bossws, jmx-console, juddi, web-console Worker Worker > > > > List of contexts to exclude from httpd registration, of the form: *host1*: > > *context1*,*host2*:*context2*,*host3*:*context3* If no host is indicated, > > it is assumed to be the default host of the server (e.g. localhost). “ROOT” > > indicates the root context. Using the default configuration, this property > > can by manipulated via the jboss.mod_cluster.excludedContexts system > > property. > > > IMHO conflict with JBEAP-5058 > Cheers, > Bogdan Sikora > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-592) https://ci.modcluster.io PGP signatures to all distributed archives

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-592?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-592: -------------------------------------- Issue Type: Task (was: Bug) > https://ci.modcluster.io PGP signatures to all distributed archives > ------------------------------------------------------------------- > > Key: MODCLUSTER-592 > URL: https://issues.jboss.org/browse/MODCLUSTER-592 > Project: mod_cluster > Issue Type: Task > Components: CI & Packaging > Reporter: Michal Karm Babacek > Assignee: Michal Karm Babacek > > Current: > {code} > httpd-2.4.25-win.64-devel.zip > httpd-2.4.25-win.64-devel.zip.sha1 > httpd-2.4.25-win.64.zip > httpd-2.4.25-win.64.zip.sha1 > {code} > Expected: > {code} > httpd-2.4.25-win.64-devel.zip > httpd-2.4.25-win.64-devel.zip.sha1 > httpd-2.4.25-win.64-devel.zip.asc > httpd-2.4.25-win.64.zip > httpd-2.4.25-win.64.zip.sha1 > httpd-2.4.25-win.64.zip.asc > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-602) Remove jboss-logging from mod_cluster code that runs on Tomcat

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-602?page=com.atlassian.jira.pl... ] Radoslav Husar reopened MODCLUSTER-602: --------------------------------------- > Remove jboss-logging from mod_cluster code that runs on Tomcat > -------------------------------------------------------------- > > Key: MODCLUSTER-602 > URL: https://issues.jboss.org/browse/MODCLUSTER-602 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Reporter: Coty Sutherland > Assignee: Radoslav Husar > > I'm trying to get rid of all of the JBoss dependencies that I can from Tomcat in JWS and found that jboss-logging is used by mod_cluster. Is it possible to remove jboss-logging from the mod_cluster code that runs on Tomcat and use JULI or some other framework? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-602) Remove jboss-logging from mod_cluster code that runs on Tomcat

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-602?page=com.atlassian.jira.pl... ] Radoslav Husar closed MODCLUSTER-602. ------------------------------------- Resolution: Rejected > Remove jboss-logging from mod_cluster code that runs on Tomcat > -------------------------------------------------------------- > > Key: MODCLUSTER-602 > URL: https://issues.jboss.org/browse/MODCLUSTER-602 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Reporter: Coty Sutherland > Assignee: Radoslav Husar > > I'm trying to get rid of all of the JBoss dependencies that I can from Tomcat in JWS and found that jboss-logging is used by mod_cluster. Is it possible to remove jboss-logging from the mod_cluster code that runs on Tomcat and use JULI or some other framework? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-602) Remove jboss-logging from mod_cluster code that runs on Tomcat

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-602?page=com.atlassian.jira.pl... ] Radoslav Husar closed MODCLUSTER-602. ------------------------------------- Resolution: Won't Do > Remove jboss-logging from mod_cluster code that runs on Tomcat > -------------------------------------------------------------- > > Key: MODCLUSTER-602 > URL: https://issues.jboss.org/browse/MODCLUSTER-602 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Reporter: Coty Sutherland > Assignee: Radoslav Husar > > I'm trying to get rid of all of the JBoss dependencies that I can from Tomcat in JWS and found that jboss-logging is used by mod_cluster. Is it possible to remove jboss-logging from the mod_cluster code that runs on Tomcat and use JULI or some other framework? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-610) IP address conversion to domain name

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-610?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-610: ------------------------------------------- [~mmadzin] Ping.^ > IP address conversion to domain name > ------------------------------------ > > Key: MODCLUSTER-610 > URL: https://issues.jboss.org/browse/MODCLUSTER-610 > Project: mod_cluster > Issue Type: Bug > Components: Core & Container Integration (Java) > Affects Versions: 1.3.7.Final > Environment: Tested on RHEL 7 > Reporter: Matus Madzin > Assignee: Radoslav Husar > > Worker is trying to obtain domain name before sends MCMP message even IP address was advertised from balancer. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 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 2018