Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] database loader job with START_TO_START_INTERVAL

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] database loader job with START_TO_START_INTERVAL

Chronological Thread 
  • From: Scott Koranda <>
  • To: Bruno Wolff III <>
  • Cc: Chris Hyzer <>, grouper-users <>
  • Subject: Re: [grouper-users] database loader job with START_TO_START_INTERVAL
  • Date: Wed, 9 Jul 2014 14:51:29 -0500

Hi Bruno,

The problem is that I need the single instance of the loader to always
be running, and it is the scheduling capabilities of the loader that I
need to work with. CRON and START_TO_START_INTERVAL are close to what
I need but not quite. I am sure I can figure out a plan to get buy.



On Wed, Jul 9, 2014 at 2:28 PM, Bruno Wolff III
> On Wed, Jul 09, 2014 at 02:08:28PM -0500,
> Scott Koranda
> <>
> wrote:
>> Understood.
>> This issue is that we want the loader jobs to run as often as possible
>> to help beat down provisioning latency. But at certain times of the
>> year (when semesters turn over) the amount of work, and hence the
>> amount of time it takes for the loader job to run, spikes. The danger
>> then is that two instances run at the same time.
>> I do not see how to reconcile those requirements/needs with CRON so I
>> was testing the START_TO_START_INTERVAL functionality, but I did not
>> expect random start times.
>> I appreciate any recommendations you can make.
> If you have systemd on these machines, you might consider using a timer
> unit. It looks like you should be able to specify a delay since the last run
> of the unit finished before restarting it. That would avoid overlapping
> runs.

Archive powered by MHonArc 2.6.16.

Top of Page