volunteering to enhance docs for mod_jk local_worker_only (server quiescence)

[Michael Greer <mi...@earthlink.net>]

I have been looking around the web to figure out how to implement 
server quiescence (starving sessions from server in balanced set to 
take it down for maintenance). The documentation on the jakarta site 
confused me, and it looks like I am not alone. More people have 
questions than answers.

I think the trouble it that the docs start with the properties, and 
then describe their complex interactions and possible outcomes. It 
might be helpful to write a HOWTO starting from the use case instead: 
HOWTO Quiesce Load-balanced Tomcat Server.

Should I take the trouble? Does this belong instead on the Apache wiki? 
I will need some help to get it right, so I wrote here to see if I 
could post drafts and get corrections from the community.

thanks,
-Michael Greer


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: volunteering to enhance docs for mod_jk local_worker_only (server quiescence)

[Michael Greer <mi...@earthlink.net>]

Ah, I extrapolated from the jk2 docs:

workers.properties:
	worker.status.type=status
httpd.conf:
	JkMount /jkstatus/* status

Nice!
-Michael Greer

On Feb 22, 2005, at 1:01 AM, Michael Greer wrote:

> Mladen,
> Built new jk from CVS. How to I access the lovely status page? 
> "/jkstatus" as in jk2? Do have to enable it? Docs do not seem to be 
> updated yet.
> Looking forward to playing with it!
> thanks,
>
-Michael Greer
>
> On Feb 19, 2005, at 2:44 PM, Mladen Turk wrote:
>
>> Michael Greer wrote:
>>> Mladen ,
>>> That sounds like the right solution! I think I remember the status 
>>> page from jk2, and it is a good idea.
>>
>> Yes, we are trying to backport all goodies from jk2 now that is
>> deprecated and no longer maintained.
>> Not only that. It will have options to fully edit properties, as well
>> to add or disable uri mappings, to reflect the dynamic deployment in
>> tomcat. You can try new features either from cvs, or wait for a
>> public beta release, before releasing stable version.
>>
>> Regards,
>> Mladen.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: volunteering to enhance docs for mod_jk local_worker_only (server quiescence)

[Michael Greer <mi...@earthlink.net>]

Mladen,
Built new jk from CVS. How to I access the lovely status page? 
"/jkstatus" as in jk2? Do have to enable it? Docs do not seem to be 
updated yet.
Looking forward to playing with it!
thanks,

-Michael Greer

On Feb 19, 2005, at 2:44 PM, Mladen Turk wrote:

> Michael Greer wrote:
>> Mladen ,
>> That sounds like the right solution! I think I remember the status 
>> page from jk2, and it is a good idea.
>
> Yes, we are trying to backport all goodies from jk2 now that is
> deprecated and no longer maintained.
> Not only that. It will have options to fully edit properties, as well
> to add or disable uri mappings, to reflect the dynamic deployment in
> tomcat. You can try new features either from cvs, or wait for a
> public beta release, before releasing stable version.
>
> Regards,
> Mladen.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: volunteering to enhance docs for mod_jk local_worker_only (server quiescence)

[Mladen Turk <ml...@jboss.com>]

Michael Greer wrote:
> Mladen ,
> That sounds like the right solution! I think I remember the status page 
> from jk2, and it is a good idea.

Yes, we are trying to backport all goodies from jk2 now that is
deprecated and no longer maintained.
Not only that. It will have options to fully edit properties, as well
to add or disable uri mappings, to reflect the dynamic deployment in
tomcat. You can try new features either from cvs, or wait for a
public beta release, before releasing stable version.

Regards,
Mladen.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: volunteering to enhance docs for mod_jk local_worker_only (server quiescence)

[Michael Greer <mi...@earthlink.net>]

Mladen ,
That sounds like the right solution! I think I remember the status page 
from jk2, and it is a good idea.
-Michael Greer

On Feb 19, 2005, at 2:29 PM, Mladen Turk wrote:

> Michael Greer wrote:
>> Should I take the trouble?
>
> local_worker and local_worker_only flags will be deprecated.
> (already are with the current 1.2.9-dev)
> There has been more powerful mechanism implemented, that is
> IMO more clearer and acts like it should.
> 1.2.9 has shared memory and status page that can be used to
> dynamically change worker properties at runtime, without
> the need for graceful restarts, or something like.
>
> New directives like 'redirect' (for preferred failover),
> 'disabled' and 'sticky_session_force' has been added.
>
> The documentation will be updated accordingly.
> Release plan is for the first half of march.
>
> Like you said the entire concept of local_worker and
> local_worker_only was too fuzzy and understandable to
> a wider audience.
>
>
> Regards,
> Mladen.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org

Re: volunteering to enhance docs for mod_jk local_worker_only (server quiescence)

[Mladen Turk <ml...@jboss.com>]

Michael Greer wrote:
> 
> Should I take the trouble?

local_worker and local_worker_only flags will be deprecated.
(already are with the current 1.2.9-dev)
There has been more powerful mechanism implemented, that is
IMO more clearer and acts like it should.
1.2.9 has shared memory and status page that can be used to
dynamically change worker properties at runtime, without
the need for graceful restarts, or something like.

New directives like 'redirect' (for preferred failover),
'disabled' and 'sticky_session_force' has been added.

The documentation will be updated accordingly.
Release plan is for the first half of march.

Like you said the entire concept of local_worker and
local_worker_only was too fuzzy and understandable to
a wider audience.


Regards,
Mladen.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org