Skip to Content.
Sympa Menu

grouper-users - [grouper-users] RE: High availability of Grouper's processes

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] RE: High availability of Grouper's processes

Chronological Thread 
  • From: Chris Hyzer <>
  • To: Gagné Sébastien <>, "" <>
  • Subject: [grouper-users] RE: High availability of Grouper's processes
  • Date: Sat, 11 Feb 2012 04:56:04 +0000
  • Accept-language: en-US

Our current solution is to monitor the processes with this WS servlet:


At Penn we do this with nagios.  It will send an email if there is a job which doesn’t run within in allotted amount of time.  We have never had to run the daemons on another server, not sometimes if the loader job has unresolvable subjects we get an email and need to adjust the query and rerun the job manually.


It would be bad if the daemon was running on more than one server at one time, so the manual failover seems like the right thing to do (reduces chance of false positives).  But if you wanted it automatic I could picture checking the daemon loader process to see if it is running and if not kick it off somewhere else…  at some point we would like to run the loader in a webapp (WS?) fyi…





From: [mailto:] On Behalf Of Gagné Sébastien
Sent: Friday, February 10, 2012 4:06 PM
Subject: [grouper-users] High availability of Grouper's processes



We want to deploy Grouper in a High Availability environment and I have a few last questions regarding Grouper’s processes. Here I’m talking about provisioning (LDAPPCNG), the Grouper Deamon (Grouper Loader) and the Group Loader. Is there a way to have those in High Availability ?


What I found in previous discussion is people have the Ui/Tomcat on 2 load balanced Hosts, but only have one server running the Grouper Processes and, should a failure happen, they would start them on the second server. My guess is that it’s still the case, but maybe I’m wrong. Is there any new development or solution for this problem ? Any synchronisation available ?


Maybe one idea would be to have a scheduler/watcher check the first server’s health and if it fails it would automatically start the processes on the second one.




PS. Will all this change with real-time provisioning ? From the quick glance I had from TomZ’s manual it seems the real-time provisioning is in the Grouper Loader so I think my question still stands for this.



Sébastien Gagné,     | Analyste en informatique

514-343-6111 x33844  | Université de Montréal,

                     | Pavillon Roger-Gaudry, local X-100-11


Archive powered by MHonArc 2.6.16.

Top of Page