[Building Sakai] Preventing ScheduledInvocationRunner from running on a node

[David Adams]

We ran into similar problems when we tried to add an "admin" server to
our cluster with a different URL. The practice of background jobs
self-registering and being completely unmanageable is very problematic.
Seems like at the very simplest, you could just add a property that
would allow disabling this job on a per-server basis. Sample patch
attached.

I can't see any reason why disabling this on one or a few nodes would
be a problem so long as it's running somewhere.

-dave

Seth Theriault wrote:
> Hello,
>
> By default, a Sakai server registers a ScheduledInvocationRunner job
> at startup. This job runs every 10 minutes and queries the
> SCHEDULER_DELAYED_INVOCATION table for tasks to be executed. Reminders
> and notifications from Evaluation, Forums, and Content are done this
> way.
>
> I am wondering if there is any danger in NOT registering this job on a
> single node in a cluster of Sakai servers. Locally, we have a "feeds"
> server that is not user-facing but accesses the same database and
> other data -- including this table -- as the other servers. People are
> getting reminders from this server -- which has a different URL -- and
> it's confusing.
>
> Looking at:
>
> jobscheduler/scheduler-component-shared/src/java/org/sakaiproject/component/app/scheduler/ScheduledInvocationManagerImpl.java
>
> there doesn't currently seem to be a method to prevent
> auto-registration of the job on a particular node, but I think that
> could be easily done.
>
> Opinions?
>
> Seth
-------------- next part --------------
A non-text attachment was scrubbed...
Name: disable-sir.patch
Type: application/octet-stream
Size: 1287 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130321/54c5277a/attachment.obj