Grouper Users - Open Discussion List

[Shilen Patel <>]

Yeah you should see a row about every 10 seconds.  I believe 
job_schedule_type would be null when it runs via the daemon.  If you don’t 
run it manually, are you seeing that additions in the temp changelog are 
being cleared out?

- Shilen

On 1/21/19, 6:20 AM, "Scott Koranda" 
<>
 wrote:

    Hi,
    
    > The only thing that should be inserting to those table is that daemon
    > job.  So I don’t know how you got duplicates in there.  And even if
    > you had multiple instances of the job running at the same time
    > somehow, the transactions in the database should have still prevented
    > the duplicates.  What database are you using?  
    
    ProxySQL (MySQL):
    
    
https://urldefense.proofpoint.com/v2/url?u=https-3A__proxysql.com_&d=DwIDaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=sWqutME58phurE0oO57Icg&m=8ILAaohKqBzWI0xcb1zDDuJfqyGfgprUKI9EPb8dIjk&s=8IxiTIjmGd2kIo7-aCe4AAe-XoetLhl308HYVzzXnnY&e=
    
    > If you look at your
    > loader logs (grouper_loader_log) during the time when that member was
    > created, do you see any signs that multiple instances of
    > CHANGE_LOG_changeLogTempToChangeLog were running at the same time?
    
    I do not believe so, but I am confused by what I am seeing in the
    grouper_loader_log.
    
    When I do
    
    SELECT job_name,job_schedule_type,started_time,status FROM 
grouper_loader_log WHERE job_name LIKE '%changeLogTempToChangeLog%'
    
    I only see rows that have job_schedule_type 'MANUAL_FROM_GSH'.
    
    Those appear to be the jobs I ran by hand using GSH to try and sort this
    issue.
    
    Should I see other entries for the change log temp to change log jobs?
    
    The only property we have overridden in grouper-loader.properties
    related to the change log is
    
    # every 10 seconds
    changeLog.changeLogTempToChangeLog.quartz.cron = 0/10 * * * * ?
    
    Thanks,
    
    Scott K