November 2016 - mod_cluster-issues

[JBoss JIRA] (MODCLUSTER-420) Drop support for httpd older than 2.4

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-420: ------------------------------------------- Lets get back to the original plan and drop these in master. > Drop support for httpd older than 2.4 > ------------------------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Task > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Drop support for httpd older than 2.4

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-420: -------------------------------------- Summary: Drop support for httpd older than 2.4 (was: Drop old httpd support) > Drop support for httpd older than 2.4 > ------------------------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Task > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Drop old httpd support

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-420: -------------------------------------- Priority: Minor (was: Major) > Drop old httpd support > ---------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Task > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Michal Karm Babacek > Priority: Minor > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Drop old httpd support

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-420: -------------------------------------- Issue Type: Task (was: Feature Request) > Drop old httpd support > ---------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Task > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Michal Karm Babacek > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Drop old httpd support

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-420: -------------------------------------- Summary: Drop old httpd support (was: Move private API dependent code to a separate layer and drop old httpd) > Drop old httpd support > ---------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Feature Request > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Michal Karm Babacek > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-420) Drop old httpd support

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-420?page=com.atlassian.jira.pl... ] Radoslav Husar reassigned MODCLUSTER-420: ----------------------------------------- Assignee: Radoslav Husar (was: Michal Karm Babacek) > Drop old httpd support > ---------------------- > > Key: MODCLUSTER-420 > URL: https://issues.jboss.org/browse/MODCLUSTER-420 > Project: mod_cluster > Issue Type: Task > Components: Native (httpd modules) > Affects Versions: 1.3.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 2.0.0.Alpha1 > > > The EWS is built on 2.2.24 and further on when productizing modcluster, this version might even increase. Lets consider dropping older versions prior to this one. > If the decision is made, you can assign to me to remove the support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-550) Failover targets should be chosen deterministically

by Michal Karm Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-550?page=com.atlassian.jira.pl... ] Michal Karm Babacek updated MODCLUSTER-550: ------------------------------------------- Tester: Michal Karm Babacek > Failover targets should be chosen deterministically > --------------------------------------------------- > > Key: MODCLUSTER-550 > URL: https://issues.jboss.org/browse/MODCLUSTER-550 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.13.Final, 1.3.5.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 2.0.0.Alpha1, 1.2.14.Final, 1.3.6.Final > > > Under the following conditions: > 1. A request arrives for a session with an unknown route > 2. A request arrives for a session with a known route in an error state, or if the intended worker is unresponsive and needs to failover > ... the failover target must be chosen in a deterministic way. This is meant to mitigate the situation where concurrent requests failover to different nodes and cause cluster-wide contention for the session. Given a consistent ordering of workers (e.g. lexographically), the failover target should be chosen by something like: hash code of session id % active worker count. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-550) Failover targets should be chosen deterministically

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-550?page=com.atlassian.jira.pl... ] Paul Ferraro updated MODCLUSTER-550: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_proxy_cluster/pull/8, https://github.com/modcluster/mod_cluster/pull/227, https://github.com/modcluster/mod_cluster/pull/228 > Failover targets should be chosen deterministically > --------------------------------------------------- > > Key: MODCLUSTER-550 > URL: https://issues.jboss.org/browse/MODCLUSTER-550 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.13.Final, 1.3.5.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 2.0.0.Alpha1, 1.2.14.Final, 1.3.6.Final > > > Under the following conditions: > 1. A request arrives for a session with an unknown route > 2. A request arrives for a session with a known route in an error state, or if the intended worker is unresponsive and needs to failover > ... the failover target must be chosen in a deterministic way. This is meant to mitigate the situation where concurrent requests failover to different nodes and cause cluster-wide contention for the session. Given a consistent ordering of workers (e.g. lexographically), the failover target should be chosen by something like: hash code of session id % active worker count. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-551) Fix spelling of EnableMCPMReceive option

by Paul Ferraro (JIRA)

Paul Ferraro created MODCLUSTER-551: --------------------------------------- Summary: Fix spelling of EnableMCPMReceive option Key: MODCLUSTER-551 URL: https://issues.jboss.org/browse/MODCLUSTER-551 Project: mod_cluster Issue Type: Bug Components: Native (httpd modules) Affects Versions: 1.3.5.Final, 1.2.13.Final Reporter: Paul Ferraro Assignee: Jean-Frederic Clere This should be spelled EnableMCMPReceive. To fix, we'll need to create a separate option, and log a warning if someone tries to configure the old one (to indicate that it is deprecated). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-550) Failover targets should be chosen deterministically

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-550?page=com.atlassian.jira.pl... ] Paul Ferraro reassigned MODCLUSTER-550: --------------------------------------- Assignee: Paul Ferraro (was: Radoslav Husar) > Failover targets should be chosen deterministically > --------------------------------------------------- > > Key: MODCLUSTER-550 > URL: https://issues.jboss.org/browse/MODCLUSTER-550 > Project: mod_cluster > Issue Type: Bug > Components: Native (httpd modules) > Affects Versions: 1.2.13.Final, 1.3.5.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 2.0.0.Alpha1, 1.2.14.Final, 1.3.6.Final > > > Under the following conditions: > 1. A request arrives for a session with an unknown route > 2. A request arrives for a session with a known route in an error state, or if the intended worker is unresponsive and needs to failover > ... the failover target must be chosen in a deterministic way. This is meant to mitigate the situation where concurrent requests failover to different nodes and cause cluster-wide contention for the session. Given a consistent ordering of workers (e.g. lexographically), the failover target should be chosen by something like: hash code of session id % active worker count. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 5 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 2016