[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [Fedora-directory-users] How to make application connect to multi-master set-up?

Interesting question. Yes a hardware load balancers works perfectly. In the configuration of a load balancer you create a virtual IP address and it will split off the requests between two servers.

I accomplished rougly the same thing with linux-ha. I created two Virtual IP addresses. Pointed half the apps at one and half the apps at the other. Both of them will fail over to the other side.

What I want to do but did not have the time is use the Linux Virtual Server Project. Ontop of linux-HA. In this way the VIRTUAL IP can float between the two productions systems. That is really the best way to go. (and you save on the cost of load balancing hardware)

There might be some ldap proxy software (sun makes something I think) that can prooxy ldap and redirect it in a HA type way. I have not looked into that. If you go with the linux virtual server project keep me in the loop. Let me know how it turns out.


On 2/19/07, Ankur Agarwal <ankur_agwal yahoo com> wrote:
We have a weblogic app server based application which talks to RedHat LDAP through weblogic's security provider APIs.
On Production env we have set-up master-master LDAP servers i.e. there are two master LDAP servers. How should i make my application connect to these 2 servers?
Should there be a front-end load balancer to which my application will make request and then load balancer will handle requests to one of the LDAP servers?
Also note that we have weblogic cluster in Prod with 2 instances. So should i make each instance point to one LDAP server? But in that case how will automatic failover work if one of the LDAP servers go down?
Would be great if people can suggest any standard solution to deal with such situations. 

The fish are biting.
Get more visitors on your site using Yahoo! Search Marketing.

Fedora-directory-users mailing list
Fedora-directory-users redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]