Grouper Users - Open Discussion List

[Scott Koranda <>]

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://proxysql.com/

> 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