Grouper Users - Open Discussion List

[Reid Watson <>]

Hi Chris,  

I have the same understanding but I really need to understand the logic 
because at the moment it seems our incremental changes aren’t triggered after 
the full sync (300 seconds), incremental changes are processed at a later 
stage (I need to dig through the logs to provide more details). The problem 
for us is the delay time for incremental to trigger. 

There was a ticket logged “https://todos.internet2.edu/browse/GRP-2216” 
“PSPNG Patch 8" so I’m wondering if there still some small issues around Full 
and Incremental sync. 

Cheers

Reid 
  

> On 1/08/2019, at 2:01 AM, Hyzer, Chris <> wrote:
> 
> My understanding is incremental sync gives way to full sync...  if it were 
> the other way then the calculations for full sync would be invalid once the 
> incremental sync makes changes... right?
> 
> -----Original Message-----
> From:  
> <> On Behalf Of Reid Watson
> Sent: Monday, July 29, 2019 12:20 AM
> To: 
> Subject: [grouper-users] Question pspng full and incremental sync
> 
> Hi All, 
> 
> Would it be possible to shed some light or input on our concern. 
> 
> Below is an example when full sync and incremental sync both intending to 
> update the same group.
> Our understanding is the Full sync is supposed to give way to incremental 
> sync after 300 seconds but it fails to do so and reset the timer again for 
> 300 seconds.
> 
> 2019-07-29 11:57:50,730: [DefaultQuartzScheduler_Worker-4] WARN  
> ProvisionerCoordinator$ProvisioningStatus.lockForIncrementalProvisioningWhenNoFullSyncIsUnderway(129)
>  -  - pspng_activedirectory: Cannot start Incremental Provisioning of 
> ec.auckland.ac.nz:LMSPersonOfInterest/#595656(Existing). FullSync underway 
> since Mon Jul 29 11:46:45 NZST 2019. We'll give up and move ahead anyway in 
> 9 seconds
> 2019-07-29 11:58:00,730: [DefaultQuartzScheduler_Worker-4] WARN  
> ProvisionerCoordinator$ProvisioningStatus.lockForIncrementalProvisioningWhenNoFullSyncIsUnderway(148)
>  -  - pspng_activedirectory: Giving up on coordination efforts between full 
> and incremental provisioning
> 2019-07-29 11:58:00,731: [DefaultQuartzScheduler_Worker-4] WARN  
> ProvisionerCoordinator$ProvisioningStatus.lockForIncrementalProvisioningWhenNoFullSyncIsUnderway(129)
>  -  - pspng_activedirectory: Cannot start Incremental Provisioning of 
> ec.auckland.ac.nz:LMSPersonOfInterest/#595656(Existing). FullSync underway 
> since Mon Jul 29 11:46:45 NZST 2019. We'll give up and move ahead anyway in 
> 300 seconds
> 2019-07-29 11:58:02,791: [FullSyncer(pspng_activedirectory)-Thread] INFO  
> ProgressMonitor.logProgressIfNecessary(106) -  - Fetching subjects 
> Progress: 31605 of 62982 (50%) in 10m:22s (3000 items/min overall, 3100 
> items/min recently). 31377 work to go, ETA: 10m:02s
> 2019-07-29 11:58:10,731: [DefaultQuartzScheduler_Worker-4] WARN  
> ProvisionerCoordinator$ProvisioningStatus.lockForIncrementalProvisioningWhenNoFullSyncIsUnderway(129)
>  -  - pspng_activedirectory: Cannot start Incremental Provisioning of 
> ec.auckland.ac.nz:LMSPersonOfInterest/#595656(Existing). FullSync underway 
> since Mon Jul 29 11:46:45 NZST 2019. We'll give up and move ahead anyway in 
> 289 seconds
> 
> Questions 
> 
> 1. Is our assumption correct how PSPNG full and incremental sync should 
> work ? 
> 2. Has anyone elate experienced this issue with PSPNG ? 
> 
> Version: 2.4.0 
> Patch Version 
> - API 64 
> - UI 38 
> - WS 6 
> - Pspng 8 
> 
> Cheers
> 
> Reid