Grouper Users - Open Discussion List

[Scott Koranda <>]

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.

Thanks,

Scott

On Wed, Jul 9, 2014 at 2:03 PM, Chris Hyzer 
<>
 wrote:
> Hmmmm, yes, you would :)
>
> For a while now I have always used cron scheduling.  Pick a random time for 
> it to run and run it every hour at that time (so they don’t all run at the 
> same time).  Then you can have a better idea about this :)
>
> Thanks,
> Chris
>
>
> -----Original Message-----
> From: Scott Koranda 
> [mailto:]
> Sent: Wednesday, July 09, 2014 3:01 PM
> To: Chris Hyzer
> Cc: grouper-users
> Subject: Re: [grouper-users] database loader job with 
> START_TO_START_INTERVAL
>
> Thanks.
>
> If I kick one off manually do I have to worry about the possibility of
> two running simultaneously, or will having one instance running
> prevent the other one from running?
>
> Thanks,
>
> Scott
>
> On Wed, Jul 9, 2014 at 1:58 PM, Chris Hyzer 
> <>
>  wrote:
>> It doesn’t necessarily start when the loader starts:
>>
>>       //start time is the interval seconds / 5, rand
>>       int startSeconds = (int)(Math.random() * intervalSeconds);
>>       Date startTime = new Date(System.currentTimeMillis() + 
>> (startSeconds*1000));
>>
>> Don’t want all START_TO_STARTs to start when the loader starts or you 
>> could have performance problems :)
>>
>> If you want to kick one off manually, you can do that from GSH:
>>
>> https://spaces.internet2.edu/display/Grouper/GrouperShell+%28gsh%29#GrouperShell%28gsh%29-Loader
>>
>> Thanks,
>> Chris
>>
>> -----Original Message-----
>> From: 
>> 
>>  
>> [mailto:]
>>  On Behalf Of Scott Koranda
>> Sent: Wednesday, July 09, 2014 1:46 PM
>> To: grouper-users
>> Subject: [grouper-users] database loader job with START_TO_START_INTERVAL
>>
>> Hi,
>>
>> I created a loader job that uses START_TO_START_INTERVAL with an
>> interval of 3600 seconds.
>>
>> My understanding is that when I restart the loader process the loader
>> job should start immediately, and then run again one hour after it
>> completes.
>>
>> Is that correct?
>>
>> I do not see any evidence in grouper_error.log (at the INFO level)
>> that the loader started the job after it was restarted. Should I?
>>
>> Thanks,
>>
>> Scott