May 2014 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-409) add VERSION method to MCMP

by Roman Jurkov (JIRA)

Roman Jurkov created MODCLUSTER-409: --------------------------------------- Summary: add VERSION method to MCMP Key: MODCLUSTER-409 URL: https://issues.jboss.org/browse/MODCLUSTER-409 Project: mod_cluster Issue Type: Feature Request Reporter: Roman Jurkov Assignee: Jean-Frederic Clere Priority: Minor add new method to MCMP "VERSION" that will output version of mod_cluster, that way clients could be written with backwards compatibility easier. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Radoslav Husar commented on MODCLUSTER-408: ------------------------------------------- {quote}But I also note the undeploy as a whole is still progressing during the request draining. Should we expect mod_cluster to delay the undeploy until requests are drained or the stop-context- timeout passes?{quote} There is not much we can do until we support a form of graceful shutdown, i.e. WFLY-1247. The best is for the customer to draing the sessions first using the console and then proceed with the shutdown. > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Aaron Ogburn commented on MODCLUSTER-408: ----------------------------------------- PR linked with a fix to the MCMP STOP-APP response issue. But I also note the undeploy as a whole is still progressing during the request draining. Should we expect mod_cluster to delay the undeploy until requests are drained or the stop-context-timeout passes? > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-408: ------------------------------------ Description: mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. was: mod_cluster doesn't properly drain requests during undeploy and/or shutdown. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests. It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-408: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/modcluster/mod_cluster/pull/81 > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown before it sends REMOVE-APP. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests and so the JBoss side thinks requests are drained. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Requests are not properly drained during undeploy

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-408: ------------------------------------ Summary: Requests are not properly drained during undeploy (was: Request are not properly drained during undeploy) > Requests are not properly drained during undeploy > ------------------------------------------------- > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Request are not properly drained during undeploy

by Aaron Ogburn (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-408?page=com.atlassian.jira.pl... ] Aaron Ogburn updated MODCLUSTER-408: ------------------------------------ Description: mod_cluster doesn't properly drain requests during undeploy and/or shutdown. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests. It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. was: mod_cluster doesn't properly drain requests during undeploy and/or shutdown. TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests. It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. > Request are not properly drained during undeploy > ------------------------------------------------ > > Key: MODCLUSTER-408 > URL: https://issues.jboss.org/browse/MODCLUSTER-408 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > mod_cluster doesn't properly drain requests during undeploy and/or shutdown. org.jboss.modcluster TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests. > It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-408) Request are not properly drained during undeploy

by Aaron Ogburn (JIRA)

Aaron Ogburn created MODCLUSTER-408: --------------------------------------- Summary: Request are not properly drained during undeploy Key: MODCLUSTER-408 URL: https://issues.jboss.org/browse/MODCLUSTER-408 Project: mod_cluster Issue Type: Bug Affects Versions: 1.2.8.Final Reporter: Aaron Ogburn Assignee: Jean-Frederic Clere mod_cluster doesn't properly drain requests during undeploy and/or shutdown. TRACE logging shows JBoss receives a STOP-APP response indicating 0 requests. It looks like mod_cluster only sets "BALANCER_CONTEXT_ID" when a worker is selected by "internal_find_best_byrequests". So it doesn't count stickied requests and allows shutdown to proceed even if stickied requests are in progress. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-209) mod_cluster_manager need better presentation

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-209?page=com.atlassian.jira.pl... ] Radoslav Husar updated MODCLUSTER-209: -------------------------------------- Fix Version/s: 1.3.1.Final > mod_cluster_manager need better presentation > -------------------------------------------- > > Key: MODCLUSTER-209 > URL: https://issues.jboss.org/browse/MODCLUSTER-209 > Project: mod_cluster > Issue Type: Enhancement > Affects Versions: 1.1.1.Final > Reporter: Anders Welen > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 1.3.1.Final > > > The mod_cluster_manager "show INFO output" status page has the following problems: > 1. "Transferred" misspelled > 2. Context is missing the number of requests > PS. Why not make it easier to parse? look at mod_jk that support both properties and XML DS. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-404) ModClusterService stop commands are always draining sessions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-404?page=com.atlassian.jira.pl... ] RH Bugzilla Integration updated MODCLUSTER-404: ----------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1098576 > ModClusterService stop commands are always draining sessions > ------------------------------------------------------------ > > Key: MODCLUSTER-404 > URL: https://issues.jboss.org/browse/MODCLUSTER-404 > Project: mod_cluster > Issue Type: Bug > Affects Versions: 1.3.0.Final, 1.2.8.Final > Reporter: Aaron Ogburn > Assignee: Jean-Frederic Clere > > Using the ModClusterService stop or stopContext commands via CLI always fails to move a context to the STOPPED state after failing to drain the active sessions. So these commands then aren't very useful for quickly stopping the context when desired if you can't do it without draining. > I think it'd make sense for any draining done by manual stops to also follow the session draining strategy used by typical stops from undeploy events. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues May 2014