February 2014 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-387) "Elected" and "Connected" values are incorrect with higher load

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-387?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-387: -------------------------------------- Labels: native (was: ) > "Elected" and "Connected" values are incorrect with higher load > --------------------------------------------------------------- > > Key: MODCLUSTER-387 > URL: https://issues.jboss.org/browse/MODCLUSTER-387 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.3.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Priority: Minor > Labels: native > Fix For: 1.3.1.Final > > > See comment https://issues.jboss.org/browse/MODCLUSTER-383?focusedCommentId=12941306&... > Marking as minor as I am not aware of some significant consequence this would cause. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-387) "Elected" and "Connected" values are incorrect with higher load

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-387?page=com.atlassian.jira.pl... ] Michal Babacek commented on MODCLUSTER-387: ------------------------------------------- Hey guys, this is a small heads-up from today's run on {{mod_cluster 1.3.1, HEAD:88040c37}}: |Balancer: qacluster|...|Status: OK|Elected: 74381|Read: 74387|Transferred: 0|Connected: -5|Load: 80| |Balancer: qacluster|...|Status: OK|Elected: 97760|Read: 97769|Transferred: 0|Connected: -2|Load: 88| |Balancer: qacluster|...|Status: OK|Elected: 107515|Read: 107390|Transferred: 0|Connected: 134|Load: 86| |Balancer: qacluster|...|Status: OK|Elected: 114849|Read: 114861|Transferred: 0|Connected: -1|Load: 84| |Balancer: qacluster|...|Status: OK|Elected: 123209|Read: 123223|Transferred: 0|Connected: -3|Load: 83| |Balancer: qacluster|...|Status: OK|Elected: 125955|Read: 125533|Transferred: 0|Connected: 433|Load: 76| |Balancer: qacluster|...|Status: NOTOK|Elected: 126348|Read: 126308|Transferred: 0|Connected: -3|Load: 76| |Balancer: qacluster|...|Status: OK|Elected: 128497|Read: 128457|Transferred: 0|Connected: -3|Load: 69| |Balancer: qacluster|...|Status: OK|Elected: 129876|Read: 129836|Transferred: 0|Connected: -4|Load: 64| |Balancer: qacluster|...|Status: OK|Elected: 132074|Read: 132032|Transferred: 0|Connected: -1|Load: 64| |Balancer: qacluster|...|Status: OK|Elected: 133995|Read: 133638|Transferred: 0|Connected: 314|Load: 62| |Balancer: qacluster|...|Status: OK|Elected: 135183|Read: 133638|Transferred: 0|Connected: 1502|Load: 62| |Balancer: qacluster|...|Status: OK|Elected: 135279|Read: 133638|Transferred: 0|Connected: 1598|Load: 62| |Balancer: qacluster|...|Status: OK|Elected: 135408|Read: 133638|Transferred: 0|Connected: 1727|Load: 62| |Balancer: qacluster|...|Status: NOTOK|Elected: 135508|Read: 134122|Transferred: 0|Connected: 45|Load: 62| |Balancer: qacluster|...|Status: NOTOK|Elected: 135508|Read: 134170|Transferred: 0|Connected: -3|Load: 62| |Balancer: qacluster|...|Status: OK|Elected: 137340|Read: 135992|Transferred: 0|Connected: 6|Load: 62| |Balancer: qacluster|...|Status: OK|Elected: 138007|Read: 136669|Transferred: 0|Connected: -4|Load: 66| |Balancer: qacluster|...|Status: OK|Elected: 138272|Read: 136933|Transferred: 0|Connected: -3|Load: 66| |Balancer: qacluster|...|Status: OK|Elected: 138842|Read: 137406|Transferred: 0|Connected: 94|Load: 69| |Balancer: qacluster|...|Status: OK|Elected: 141443|Read: 140105|Transferred: 0|Connected: -4|Load: 69| |Balancer: qacluster|...|Status: OK|Elected: 142987|Read: 141641|Transferred: 0|Connected: 4|Load: 71| |Balancer: qacluster|...|Status: OK|Elected: 145194|Read: 143793|Transferred: 0|Connected: 59|Load: 71| |Balancer: qacluster|...|Status: OK|Elected: 146071|Read: 144733|Transferred: 0|Connected: -4|Load: 73| |Balancer: qacluster|...|Status: OK|Elected: 146071|Read: 144733|Transferred: 0|Connected: -4|Load: 73| |Balancer: qacluster|...|Status: OK|Elected: 146181|Read: 144843|Transferred: 0|Connected: -4|Load: 74| |Balancer: qacluster|...|Status: OK|Elected: 146622|Read: 144972|Transferred: 0|Connected: 308|Load: 74| |Balancer: qacluster|...|Status: OK|Elected: 147216|Read: 144972|Transferred: 0|Connected: 902|Load: 74| |Balancer: qacluster|...|Status: OK|Elected: 148205|Read: 144972|Transferred: 0|Connected: 1891|Load: 74| |Balancer: qacluster|...|Status: NOTOK|Elected: 148205|Read: 144972|Transferred: 0|Connected: 1409|Load: 74| |Balancer: qacluster|...|Status: NOTOK|Elected: 148205|Read: 144972|Transferred: 0|Connected: 486|Load: 74| |Balancer: qacluster|...|Status: NOTOK|Elected: 148306|Read: 144972|Transferred: 0|Connected: 113|Load: 74| |Balancer: qacluster|...|Status: NOTOK|Elected: 150405|Read: 145874|Transferred: 0|Connected: 1308|Load: 70| |Balancer: qacluster|...|Status: NOTOK|Elected: 150405|Read: 147096|Transferred: 0|Connected: 83|Load: 70| |Balancer: qacluster|...|Status: OK|Elected: 151025|Read: 147622|Transferred: 0|Connected: 177|Load: 70| |Balancer: qacluster|...|Status: OK|Elected: 152212|Read: 148990|Transferred: 0|Connected: -4|Load: 1| |Balancer: qacluster|...|Status: OK|Elected: 152230|Read: 149008|Transferred: 0|Connected: -4|Load: 1| |Balancer: qacluster|...|Status: OK|Elected: 152235|Read: 149013|Transferred: 0|Connected: -4|Load: 1| |Balancer: qacluster|...|Status: OK|Elected: 152255|Read: 149033|Transferred: 0|Connected: -4|Load: 1| |Balancer: qacluster|...|Status: OK|Elected: 152285|Read: 149063|Transferred: 0|Connected: -4|Load: 1| |Balancer: qacluster|...|Status: OK|Elected: 152317|Read: 149094|Transferred: 0|Connected: -3|Load: 1| |Balancer: qacluster|...|Status: OK|Elected: 152317|Read: 149094|Transferred: 0|Connected: -3|Load: 1| The aforementioned is a series of "screen shots", several seconds apart, towards the end of the test, from mod_cluster manager console of a one of five present workers. It is noteworthy that all other workers presented similar erratic crazy numbers. The test was a benchmark, follow-up on [MODCLUSTER-372]/[MODCLUSTER-388], so the balancer was under a considerable load. Furthermore, one might note several {{Status: NOTOK}} messages, I'm however unable to provide any further details, because the logging was completely shut off during the perf test. In my opinion, the system might have been chocking on requests, unable to receive STATUS message in time....dunno... > "Elected" and "Connected" values are incorrect with higher load > --------------------------------------------------------------- > > Key: MODCLUSTER-387 > URL: https://issues.jboss.org/browse/MODCLUSTER-387 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.3.0.Alpha1 > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 1.3.1.Final > > > See comment https://issues.jboss.org/browse/MODCLUSTER-383?focusedCommentId=12941306&... > Marking as minor as I am not aware of some significant consequence this would cause. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-392) mod_proxy_cluster.c doesn't compile with httpd 2.2.22

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-392?page=com.atlassian.jira.pl... ] Michal Babacek updated MODCLUSTER-392: -------------------------------------- Git Pull Request: https://github.com/modcluster/mod_cluster/pull/62 > mod_proxy_cluster.c doesn't compile with httpd 2.2.22 > ----------------------------------------------------- > > Key: MODCLUSTER-392 > URL: https://issues.jboss.org/browse/MODCLUSTER-392 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.3.1.Final > Reporter: Michal Babacek > Assignee: Michal Babacek > Priority: Critical > Fix For: 1.3.1.Final > > > {code} > d_proxy_cluster.c: In function 'proxy_cluster_post_request': > mod_proxy_cluster.c:3943: error: 'proxy_worker_stat' has no member named 'name' > {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-392) mod_proxy_cluster.c doesn't compile with httpd 2.2.22

by Michal Babacek (JIRA)

Michal Babacek created MODCLUSTER-392: ----------------------------------------- Summary: mod_proxy_cluster.c doesn't compile with httpd 2.2.22 Key: MODCLUSTER-392 URL: https://issues.jboss.org/browse/MODCLUSTER-392 Project: mod_cluster Issue Type: Bug Affects Versions: 1.3.1.Final Reporter: Michal Babacek Assignee: Michal Babacek Priority: Critical Fix For: 1.3.1.Final {code} d_proxy_cluster.c: In function 'proxy_cluster_post_request': mod_proxy_cluster.c:3943: error: 'proxy_worker_stat' has no member named 'name' {code} -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-390) add failonstatus to mod_cluster

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-390?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-390: ------------------------------------------------ The failonstatus of mod_cluster behaves sightly differently to mod_jk. It is the in post-request() logic so the response is already in the buffers or sent to the client so the error code and the page from the back-end will be sent and the worker will be marked in error after that. (that is the mod_proxy_balancer feature). > add failonstatus to mod_cluster > ------------------------------- > > Key: MODCLUSTER-390 > URL: https://issues.jboss.org/browse/MODCLUSTER-390 > Project: mod_cluster > Issue Type: Enhancement > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > > The feature was added in httpd-2.2.17 in the mod_proxy_balancer we just need to copy that code and find a way to configure it, -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-390) add failonstatus to mod_cluster

by Jean-Frederic Clere (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-390?page=com.atlassian.jira.pl... ] Jean-Frederic Clere commented on MODCLUSTER-390: ------------------------------------------------ MODCLUSTER-391 isn't related to this issue. > add failonstatus to mod_cluster > ------------------------------- > > Key: MODCLUSTER-390 > URL: https://issues.jboss.org/browse/MODCLUSTER-390 > Project: mod_cluster > Issue Type: Enhancement > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > > The feature was added in httpd-2.2.17 in the mod_proxy_balancer we just need to copy that code and find a way to configure it, -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-388) Fix for MODCLUSTER-372 is broken

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-388?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-388: -------------------------------------- Summary: Fix for MODCLUSTER-372 is broken (was: MOD_CLUSTER 372 fix is broken) > Fix for MODCLUSTER-372 is broken > -------------------------------- > > Key: MODCLUSTER-388 > URL: https://issues.jboss.org/browse/MODCLUSTER-388 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.3.0.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Blocker > Fix For: 1.3.1.Final > > > A piece of the fix is missing in the release... Native part is broken. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-388) MOD_CLUSTER 372 fix is broken

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-388?page=com.atlassian.jira.pl... ] Michal Babacek commented on MODCLUSTER-388: ------------------------------------------- Linking. > MOD_CLUSTER 372 fix is broken > ----------------------------- > > Key: MODCLUSTER-388 > URL: https://issues.jboss.org/browse/MODCLUSTER-388 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.3.0.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Blocker > Fix For: 1.3.1.Final > > > A piece of the fix is missing in the release... Native part is broken. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-235) Support hot-standby worker nodes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-235?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-235: ---------------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 987259|https://bugzilla.redhat.com/show_bug.cgi?id=987259] from MODIFIED to ASSIGNED > Support hot-standby worker nodes > -------------------------------- > > Key: MODCLUSTER-235 > URL: https://issues.jboss.org/browse/MODCLUSTER-235 > Project: mod_cluster > Issue Type: Feature Request > Affects Versions: 1.1.2.Final > Reporter: Samuel Mendenhall > Assignee: Jean-Frederic Clere > > Like in mod_proxy and mod_jk, mod_cluster should support the ability to keep a worker node in hot-standby. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-391) mod_cluster and mod_proxy integration

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-391?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on MODCLUSTER-391: ---------------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 987259|https://bugzilla.redhat.com/show_bug.cgi?id=987259] from MODIFIED to ASSIGNED > mod_cluster and mod_proxy integration > ------------------------------------- > > Key: MODCLUSTER-391 > URL: https://issues.jboss.org/browse/MODCLUSTER-391 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.6.Final > Environment: All platforms we build mod_cluster for. > Reporter: Michal Babacek > Assignee: Jean-Frederic Clere > Labels: native_libraries > Fix For: 1.2.8.Final, 1.3.1.Final > > Attachments: error_log, mod_cluster.conf, mod_proxy.conf, standalone-ha.xml > > > This Jira encapsulates all concerns regarding mod_cluster - mod_proxy integration. For instance, while basic {{ProxyPass}} settings work just fine, e.g. serving some files on {{/static}} from the Apache HTTP itself: > {code} > ProxyPassMatch ^/static/ ! > ProxyPass / balancer://qacluster stickysession=JSESSIONID|jsessionid nofailover=on > ProxyPassReverse / balancer://qacluster > ProxyPreserveHost on > {code} > there are more complex setups, involving {{BalancerMember}} configurations, that do not work as expected. In the following example, one wanted to have {{/clusterbench}} application managed by mod_cluster, dynamically, while at the same time, in a different VirtualHost, having {{/tses}} application handled by manually created mod_proxy balancer settings. > Attached [^mod_cluster.conf], [^mod_proxy.conf], [^standalone-ha.xml](modcluster subsystem element only) and [^error_log]. > The aforementioned setup resulted in: > |HTTP 200|(From worker)|http://10.16.88.19:8847/clusterbench/requestinfo/|OK|(/)| > |HTTP 404|(From httpd)|http://10.16.88.19:8847/tses/session.jsp|Expected fail|(/)| > |HTTP 503|(From httpd)|http://10.16.88.19:2182/tses/session.jsp|Unexpected fail|(x)| -- 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

11 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues February 2014