You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by "Folkens, Brad" <bf...@downers.us> on 2004/04/13 17:01:45 UTC
SchedulerService in a clustered environment
Has anybody had success with the SchedulerService in a clustered
environment.
We currently are using resin as our webapp container and are considering a
move to a clustered / load balanced environment with 2 or more resin
servers. Is the SchedulerService aware of synchronization across JVMs?
Bradford A. Folkens
bfolkens@vil.downers-grove.il.us <ma...@vil.downers-grove.il.us>
Re: SchedulerService in a clustered environment
Posted by "Jeffrey D. Brekke" <jb...@wi.rr.com>.
We took the simplest route possible, and run one of our two nodes with
the scheduler service active, and the other without it active. This
works great when your scheduled services can use something like a
common database, file, or directory location.
A more robust solution would be really interesting, what did you have
in mind?
>>>>> On Tue, 13 Apr 2004 10:01:45 -0500, "Folkens, Brad" <bf...@downers.us> said:
> Has anybody had success with the SchedulerService in a clustered
> environment.
> We currently are using resin as our webapp container and are
> considering a move to a clustered / load balanced environment with 2
> or more resin servers. Is the SchedulerService aware of
> synchronization across JVMs?
> Bradford A. Folkens bfolkens@vil.downers-grove.il.us
> <ma...@vil.downers-grove.il.us>
--
=====================================================================
Jeffrey D. Brekke jbrekke@wi.rr.com
Wisconsin, USA brekke@apache.org
ekkerbj@yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: SchedulerService in a clustered environment
Posted by Brian Lawler <br...@tribenetwork.com>.
Brad-
We use the SchedulerService at tribe.net, but to my knowledge it is
most definitely not cluster aware. We actually have to go through the
trouble of deploying a single instance of the app that does the
scheduled work. Very suboptimal.
One thing that we have actually talked about doing here is actually
using cron for the scheduling and coding some very limited access
actions that do the real work. This has a number of advantages:
1) Ops people (UNIX ones anyway) know cron backwards and forwards, and
it is very good at doing what it does.
2) Cron has a good reporting mechanism built in - send stdout to an
email address.
3) The cron script may be as easy as a shell script that invokes a wget
or curl on the url of the scheduled task that sits inside your turbine
application. The result of calling that URL could be a plain text
report of how the job did.
4) Invoking turbine things through the HTTP interface has the lovely
side effect of providing you with a fully formed $data and $context
objects, so if you are doing something like sending out an automated
email you will have all of your normal tools available to pass into the
template that is the body of the email.
5) Bigger jobs can be broken into multiple small URL requests and your
load balancer will be able to decide which servers in your cluster
should do the work.
-B
On Apr 13, 2004, at 8:01 AM, Folkens, Brad wrote:
> Has anybody had success with the SchedulerService in a clustered
> environment.
>
> We currently are using resin as our webapp container and are
> considering a
> move to a clustered / load balanced environment with 2 or more resin
> servers. Is the SchedulerService aware of synchronization across JVMs?
>
> Bradford A. Folkens
> bfolkens@vil.downers-grove.il.us
> <ma...@vil.downers-grove.il.us>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
RE: SchedulerService in a clustered environment
Posted by Eric Pugh <ep...@upstate.com>.
http://xingu.sourceforge.net/ Check out the Quartz wrapper.
Eric
> -----Original Message-----
> From: Scott Eade [mailto:seade@backstagetech.com.au]
> Sent: Wednesday, April 14, 2004 7:20 PM
> To: Turbine Users List
> Subject: Re: SchedulerService in a clustered environment
>
>
> Folkens, Brad wrote:
>
> >Has anybody had success with the SchedulerService in a clustered
> >environment.
> >
> >We currently are using resin as our webapp container and are
> considering a
> >move to a clustered / load balanced environment with 2 or more resin
> >servers. Is the SchedulerService aware of synchronization across JVMs?
> >
> >Bradford A. Folkens
> >bfolkens@vil.downers-grove.il.us
> <ma...@vil.downers-grove.il.us>
> >
> As per the other responses, I am reasonably certain that the Turbine
> SchedulerService is not cluster aware. I have also been hit a couple of
> times by a problem when daylight savings ends (handled automatically on
> the server) and a scheduled task is executed repeatedly due t a bug
> somewhere (perhaps double execution I could understand, but not
> thousands of repetitions).
>
> At http://xingu.sourceforge.net/ they have a Quartz Scheduler service.
> I haven't looked at it yet, but if it is any good I would propose that
> we deprecate the TurbineSchedulerService in favour of it. According to
> it's feature list, Quartz _is_ cluster aware.
>
> Scott
>
> --
> Scott Eade
> Backstage Technologies Pty. Ltd.
> http://www.backstagetech.com.au
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: SchedulerService in a clustered environment
Posted by Scott Eade <se...@backstagetech.com.au>.
Folkens, Brad wrote:
>Has anybody had success with the SchedulerService in a clustered
>environment.
>
>We currently are using resin as our webapp container and are considering a
>move to a clustered / load balanced environment with 2 or more resin
>servers. Is the SchedulerService aware of synchronization across JVMs?
>
>Bradford A. Folkens
>bfolkens@vil.downers-grove.il.us <ma...@vil.downers-grove.il.us>
>
As per the other responses, I am reasonably certain that the Turbine
SchedulerService is not cluster aware. I have also been hit a couple of
times by a problem when daylight savings ends (handled automatically on
the server) and a scheduled task is executed repeatedly due t a bug
somewhere (perhaps double execution I could understand, but not
thousands of repetitions).
At http://xingu.sourceforge.net/ they have a Quartz Scheduler service.
I haven't looked at it yet, but if it is any good I would propose that
we deprecate the TurbineSchedulerService in favour of it. According to
it's feature list, Quartz _is_ cluster aware.
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org