Grouper Users - Open Discussion List

["Black, Carey M." <>]

Andre,

 

Maybe you are using the wrong tools in Grouper to achieve your goals?

 

My personal philosophy ( IMHO and subject to debate by the list J ) :

 

                Change Log Consumers (CLC) should be for outbound flow of changes from Grouper to other systems.

                                Note: You can also loop the CLC’s through a messaging systems for this too.

 

                Hooks are more on the “interactive UI” ( but not strictly interactive the work can be done via async to the UI threads as well) activities for the system.

 

 

Which leads me to these question:

 

                What are your CLC’s doing that you would expect to see in the UI?

                Should those things only made in Grouper after some external system state is changed?

                                Maybe that order should be changed to allow the user to “do all of their work” and “let the system process the CLC” later?

 

 

Additionally another “random” (yet maybe related) question:

                What RDMBS are you using?

                Are your DBA’s seeing any long running queries? ( If so, what are they?)

 

 

And note: You should always have at least one loader/daemon running.

                If it is not running all of the time, then there will be “a lot of work” to catch up on when it starts and that then will be an avalanche of CLC activities too. ( And some things that are done with Grouper rules will also not be enforced regularly either. )

 

--

Carey Matthew

 

From: <> On Behalf Of Hyzer, Chris
Sent: Monday, December 10, 2018 5:00 PM
To: ;
Subject: RE: [grouper-users] loader FIFO

 

The change log starts as a single queue as id’s get assigned and point in time and flattened memberships are calculated.  The UI will still work though.

 

If you have a recent grouper then you can/should run multiple loaders.  We have 2.3 at penn and run 5 loader processes.  Might be overkill, but just as a datapoint

 

Thanks

Chris

 

From: <> On Behalf Of Andre Daniels
Sent: Monday, December 10, 2018 3:48 PM
To:
Subject: [grouper-users] loader FIFO

 

Are all grouper changesets put into a single queue? It appears that new changes are starved while while large jobs are processing. Is there a way to keep the UI responsive while a sync or some other large job is being processed? Similarly, is it possible to run 2 loaders? I was cautioned not to, but I would like to have a loader that starts up periodically and runs a sync.

 

Thanks,

Andre
--

Andre Daniels 

Sr. Developer/Security Analyst

University of California Santa Cruz

(831) 459-1980