Grouper Users - Open Discussion List

[Robert Bradley <>]

In recent testing, I have been trying to assign READ access to all
groups in a particular tree (~35000 groups in total) to a group with
~1200 indirect members.  This test used Postgres 9.1 as the backend
database for Grouper 2.2.1.  The approach I used was to assign the rule
described at
https://spaces.internet2.edu/display/Grouper/Grouper+rules+use+case+-+Inherited+privileges+on+groups
to the base stem and then use RuleApi.runRulesForOwner(stem) to apply them.

The problem I'm seeing is that when the rules are applied, the change
log table size increases massively to 26 million records or more (~11 GB
for the table, with changelog indexes of >24 GB).  This caused problems
with disk space, but also creates huge multi-day lags in provisioning
new group members using PSP until the changelog clears.

I was wondering if anyone else had seen similar issues, or had
suggestions of other things to try to improve PSP performance in this
case.  On a separate note, I would be interested to hear what changelog
table sizes are typical, in case this is an issue of simply not
provisioning enough disk space for Grouper's database to use.

-- 
Dr Robert Bradley
Identity and Access Management, IT Services, University of Oxford

Attachment: signature.asc
Description: OpenPGP digital signature