Grouper Users - Open Discussion List

[Paul Engle <>]

Yeah, I'd noticed the lack of accurate timings for a full sync. That's
what led me to this. Now that I have a config I can mostly live with, I
wanted to see how long a full run would take on all the stems that are
currently being provisioned. I was excited when the grouper_loader_log
seemed to indicate that the job finished in an hour or so. Less so once
I looked at the log and realized it was actually still running its
worker threads... :)

I'm going to take a guess and say that the check was maybe supposed to
be against cache size, not batch size. That seems more reasonable to me.

  -paul

On 2/27/2017 4:04 PM, Michael R Gettes wrote:
> Yep, I saw this too.  There also doesn’t seem to be an indicator in the log 
> of start and stop of the fullsync (yes, you can consult the 
> grouper_loader_log as well).  I thought leaving the error there for now cuz 
> it easily shows when the fullsync is finished :-)  While this is humorous 
> to me, for now, the error is useful.
> 
> /mrg
> 
>> On Feb 27, 2017, at 5:00 PM, Paul Engle 
>> <>
>>  wrote:
>>
>>
>> Me again, still kicking the PSPNG tires. I seem to have hit another snag
>> once I tried to ramp up my testing.
>>
>> I have an LdapGroupProvisioner configured with grouperIsAuthoritative
>> set to true. It was working fine in my test stem that has a whopping 12
>> groups in it. Once I tried to attach the provisioner to a larger stem
>> however, I started to hit an error during group cleanup saying there
>> were too many groups to fetch.
>>
>> Poking around the code, it seems to be generated by the
>> fetchTargetSystemGroups call when the number of groups in the
>> provisioning item is larger than groupSearch_batchSize. I confirmed that
>> by going back to just my test stem and dialing down the batch size to
>> 10. Sure enough, I get the same error now. Stack trace below:
>>
>> 2017-02-27 15:21:52,500: [pspng_groupOfUniqueNames-FullSync] ERROR
>> FullSyncProvisioner.processGroupCleanup(356) -  -
>> pspng_groupOfUniqueNames: Problem doing group cleanup
>> java.lang.IllegalArgumentException:
>> LdapGroupProvisioner.fetchTargetSystemGroups: invoked with too many
>> groups to fetch
>>      at
>> edu.internet2.middleware.grouper.pspng.LdapGroupProvisioner.fetchTargetSystemGroups(LdapGroupProvisioner.java:290)
>>      at
>> edu.internet2.middleware.grouper.pspng.Provisioner.doFullSync_cleanupExtraGroups(Provisioner.java:994)
>>      at
>> edu.internet2.middleware.grouper.pspng.FullSyncProvisioner.processGroupCleanup(FullSyncProvisioner.java:347)
>>      at
>> edu.internet2.middleware.grouper.pspng.FullSyncProvisioner.thread_manageFullSyncProcessing(FullSyncProvisioner.java:180)
>>      at
>> edu.internet2.middleware.grouper.pspng.FullSyncProvisioner$1.run(FullSyncProvisioner.java:132)
>>      at java.lang.Thread.run(Thread.java:745)
>>
>>
>> The groupSearch_batchSize defaults to 50. It doesn't seem right to bump
>> the batch size up to be greater than my total number of groups in any
>> given provisioning item, which can number in the thousands.
>>
>> Has anyone else seen this?
>>
>>  -paul
>>
>>
>> -- 
>> Paul Engle
>> Office of Information Technology
>> 
>> 713-348-4702
> 
> 

-- 
Paul Engle
Office of Information Technology

713-348-4702