Skip to Content.
Sympa Menu

grouper-users - [grouper-users] PSPNG fullSync error on group cleanup

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] PSPNG fullSync error on group cleanup


Chronological Thread 
  • From: Paul Engle <>
  • To:
  • Subject: [grouper-users] PSPNG fullSync error on group cleanup
  • Date: Mon, 27 Feb 2017 16:00:19 -0600
  • Ironport-phdr: 9a23:V0Cg6x9nKp5ZNv9uRHKM819IXTAuvvDOBiVQ1KB42+scTK2v8tzYMVDF4r011RmSDNidsawP0reJ+4nbGkU4qa6bt34DdJEeHzQksu4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2aFLduGC94iAPERvjKwV1Ov71GonPhMiryuy+4ZPebgFIiTanf79/LRq6oRjRu8QUnIBvNrs/xhzVr3VSZu9Y33loJVWdnxb94se/4ptu+DlOtvwi6sBNT7z0c7w3QrJEAjsmNXs15NDwuhnYUQSP/HocXX4InRdOHgPI8Qv1Xpb1siv9q+p9xCyXNtD4QLwoRTiv6bpgRxj0hSoJNTM0/njbhtB/galGpB6spwBzz4vSbYqINvRxY7ndcMsES2RBQ8hfVCJPDY2zYIQTAOQMJvpYoovnqlcSsRezCwuhCeXywTFInH/22qg63vw7Hw7cwQwgG88FvnvSrNX6MKcdT/2+wa7QzTrdafNW1jP955bTfxA7oPGDQax/fdDPxkYyCgPIl1OdopHrMTOS0+QCqWmb7+x4WOKzi24nsR9+rSKyycs2kInJm4QVx1bZ/it62IY4PcC0RFB4bNK+H5ZcqTuWO5VqTs8/WW1kpTo2xqAetZKmYiQHy44ryhHBZ/CdboSF5hbuWPyfLDtkgn9uZaixiAyo8Ue6z+3xTsm030hOripCitTMrmgN2wLJ5sidS/ty4lmu1SyR2A/O9+FIOUE0lazFJJ492rM8i4QfvEfZEiL5hkn6lrGaelk59uSy9ujrfqjqqoeZN4BuiwH+Nqoumta4AeQ9KgUOR3aU+eKz1L3n40L0W69KjvwqnabHqpzVO9kUprOhDw9Pzokj8wq/Dyuh0NkAknkHNlVFeA+fj4f3IVHCOe34DeyhjFS2izdm3PTGPrz6ApXRNXjPjq3tfbd7605A1gUz19Zf6IxICr0fOv78RFL+tMGLRiM+ZgOuxPv/Bc84y5gTQ3mnA6mFPbnUvEPSoO8jPrqifogQ7Q70NvxtyvjhiXJxzUcQe6at0LMNaXu1WPlqPhPKMjLXnt4dHDJS7UIFR+vwhQjfCTM=


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



Archive powered by MHonArc 2.6.19.

Top of Page