Skip to Content.
Sympa Menu

grouper-dev - Re: [grouper-dev] psp - first stab.

Subject: Grouper Developers Forum

List archive

Re: [grouper-dev] psp - first stab.


Chronological Thread 
  • From: Tom Zeller <>
  • To: Lynn Garrison <>
  • Cc: Grouper Dev <>
  • Subject: Re: [grouper-dev] psp - first stab.
  • Date: Wed, 15 Feb 2012 18:28:06 -0600

The log messages :

INFO Full sync is running, returning sequence number '392'
ERROR Did not get all the way through the batch! 392 != 492

should be improved. Perhaps to :

INFO 'Just a note to let you know that since a full synchronization
of the provisioning target is being performed, the current change log
entry (sequence number 392) will be processed after the full
synchronization has been completed. Please ignore the next error
message regarding this change log entry.'

So, don't kill the loader process, let the full synchronization
finish. If you want to estimate how long it will take for a full sync
to complete, try running :

time bin/gsh.sh -psp -bulkSync

I probably should be more consistent and use one word instead of two,
'bulkSync' and 'fullSync' mean the same thing.

FWIW, of the various properties in grouper-loader.properties, those
prefixed with 'changeLog.psp.fullSync' control when full
synchronizations of provisioning targets are performed.

# To run full provisioning synchronizations periodically, provide the
class name which provides a 'public void fullSync()' method.
changeLog.psp.fullSync.class =
edu.internet2.middleware.psp.grouper.PspChangeLogConsumer

# Schedule full synchronizations. Defaults to 5 am : 0 0 5 * * ?.
changeLog.psp.fullSync.quartzCron = 0 0 5 * * ?

This last one, runAtStartup, should probably be left as false until I
think it through more thoroughly. After a full sync is performed at
startup, we should probably ignore change log entries whose timestamp
is before the time when the full synchronization began. The psp does
not currently do this, ignore entries based on timestamp, but I think
it should.

# Run a full synchronization job at startup. Defaults to false.
# changeLog.psp.fullSync.runAtStartup = false

> 2012-02-15 12:51:00,057: [DefaultQuartzScheduler_Worker-1] INFO  
> PspChangeLogConsumer.processChangeLogEntries(358) -  - PSP Consumer 'psp' -
> Full sync is running, returning sequence number '392'
> 2012-02-15 12:51:00,066: [DefaultQuartzScheduler_Worker-1] ERROR
> ChangeLogHelper.processRecords(229) -  - Did not get all the way through
> the batch! 392 != 492
> 2012-02-15 12:52:00,053: [DefaultQuartzScheduler_Worker-9] INFO  
> PspChangeLogConsumer.processChangeLogEntries(358) -  - PSP Consumer 'psp' -
> Full sync is running, returning sequence number '392'
> 2012-02-15 12:52:00,057: [DefaultQuartzScheduler_Worker-9] ERROR
> ChangeLogHelper.processRecords(229) -  - Did not get all the way through
> the batch! 392 != 492



Archive powered by MHonArc 2.6.16.

Top of Page