Grouper Users - Open Discussion List

[Jeffrey Crawford <>]

We had an interesting case show up not so long ago, basically there was a change in a group that in effect, removed everyone, and then added them all back (composite group change), there were > 122,000 members of the group so it cause a huge back log of changes that wound up taking quite a few hours.

Eventually I just stopped grouper, tagged the psp entry in the grouper_change_log_consumer, to be the same number as syncGroups and restarted, which performed a bulkSync. That only takes 30 min.

Additionally what I noticed is that our ldap servers were backed up quite a bit as they were busy deleting records one at a time, and then adding them again one at a time.

It got me to thinking that perhaps there should be a setting that will identify how many records are supposed to change from the change log and say if it's over 10,000, instead of processing the change log, it would sync up the psp record to match syncGroups, and perform a bulk sync, which is also easier on the LDAP servers as it does a compare and just modifies what needs to change.

This setting would be settable by the admin since different environments might find they should process 30,000 before the change log takes longer than a bulk sync for example

Thoughts?

Jeffrey E. Crawford
Enterprise Service Team

    ^         ^

   / \  ^    / \    ^

  /   \/ \  /   \  / \

 /        \/     \/   \

/                      \

You have been assigned this mountain to prove to others that it *can* be moved.