pvdung / pwm

Automatically exported from code.google.com/p/pwm
0 stars 0 forks source link

Clustering [Enhancement Request] #253

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
This is an enhancement request to have PWM be cluster-aware. Particularly as it 
relates to when PWM is behind Access Manager or other reverse proxy system. One 
example that I can see is to allow multiple instances of PWM to share one 
common pwmDB database instance.

Thanks.

Original issue reported on code.google.com by RailG...@gmail.com on 3 Aug 2012 at 3:15

GoogleCodeExporter commented 9 years ago
There's actually some support already for this (such as session stickyness 
detection).    The PwmDB will never span multiple servers, but each of the 
subsystems that use PwmDB for storage allow you to use a central database 
instead (storage of response questions for example).  

For now I recommend you use fail-over configuration in NAM or other device 
instead of load balancing.  For all but the largest shops a single instance 
ought to be able to handle the load.

I will keep this enhancement open as a marker until PWM has support for:

a) configuration controls to identify cluster members.
b) combined statistic/status/activity reporting
c) combined health status reporting

Original comment by jrivard on 3 Aug 2012 at 3:20

GoogleCodeExporter commented 9 years ago
Just some extra information, for if you run Tomcat, you may want to have a look 
at this: http://tomcat.apache.org/tomcat-6.0-doc/cluster-howto.html

- Menno

Original comment by menno.pi...@gmail.com on 3 Aug 2012 at 6:54

GoogleCodeExporter commented 9 years ago

Original comment by menno.pi...@gmail.com on 24 May 2013 at 9:18