Skip to Content.
Sympa Menu

grouper-users - [grouper-users] RE: Grouper Loader - Limit extreme changes

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] RE: Grouper Loader - Limit extreme changes

Chronological Thread 
  • From: Chris Hyzer <>
  • To: "Waldbieser, Carl" <>
  • Cc: grouper-users <>
  • Subject: [grouper-users] RE: Grouper Loader - Limit extreme changes
  • Date: Tue, 5 May 2015 21:50:23 +0000
  • Accept-language: en-US

Vivek Sachdeva implemented this including a unit test, thanks a lot Vivek! I
put it in the latest API patch: grouper_v2_2_1_api_patch_8

Here is the configuration in

# if the loader should check to see too many users were removed, if so, then
error out and
# wait for manual intervention
loader.failsafe.use = false

# if a group has a size less than this (default 200), then make changes
including blanking it out
loader.failsafe.minGroupSize = 200

# if a group with more members than the loader.failsafe.minGroupSize have
more than this percent (default 30)
# removed, then log it as error, fail the job, and don't actually remove the
# In order to run the job, an admin would need to change this param in the
# and run the job manually, then change this config back
loader.failsafe.maxPercentRemove = 30

Note: you have to explicitly enable this. I wonder if these defaults are
what we want... let me know your thoughts. My loader jobs run against
database that do not truncate and add members back, so I don’t really want to
have to manually go in and tell it its ok when a group changes by a lot...
maybe others disagree? :)


-----Original Message-----
From: Waldbieser, Carl

Sent: Friday, March 13, 2015 3:39 PM
To: Chris Hyzer
Cc: grouper-users
Subject: Re: Grouper Loader - Limit extreme changes


Yes, I think that would be useful.
In this case, I control the process, but I can envision scenarios where I
Also, I think I'd feel better knowing that there was a failsafe on Grouper.


----- Original Message -----
From: "Chris Hyzer"
To: "Carl Waldbieser"
Sent: Friday, March 13, 2015 2:23:52 PM
Subject: RE: Grouper Loader - Limit extreme changes

Not at the moment, it will sync with the table. Is there a way for the
process the updates the table to not truncate first and just add/remove as
needed? :) I could add an enhancement in the loader if you think it would
be useful


-----Original Message-----

On Behalf Of Waldbieser, Carl
Sent: Friday, March 13, 2015 12:26 PM
To: grouper-users
Subject: [grouper-users] Grouper Loader - Limit extreme changes

Is there some way to tell the Grouper Loader to abort a sync if it detects a
big swing in group membership?
I am thinking of the case where we have a process that populates a data
warehouse SQL database and the loader populates reference from it.
If the job failed and left a table empty, is there a way to tell the loader
not to alter the reference group?

Carl Waldbieser
ITS System Programmer
Lafayette College

  • [grouper-users] RE: Grouper Loader - Limit extreme changes, Chris Hyzer, 05/05/2015

Archive powered by MHonArc 2.6.16.

Top of Page