[Date Prev][Date Next]
Re: Failover Failure Advice
Setup two slaves behind a VIP.
Point local clients to that vip.
If load is high on them, add nodes.
Setup mirror masters - behind a vip (the prefs one server - no round robin - active/standby).
Point slaves (and perhaps any local clients) to that vip.
* If using SSL (and you should be), you'll have to use either wildcard certs or certs using hostname of the vip.
Chris Jacobs, Systems Administrator
Apollo Group | Apollo Marketing | Aptimus
2001 6th Ave Ste 3200 | Seattle, WA 98121
phone: 206.839-8245 | cell: 206.601.3256 | Fax: 208.441.9661
From: openldap-technical-bounces@OpenLDAP.org <openldap-technical-bounces@OpenLDAP.org>
To: firstname.lastname@example.org <email@example.com>
Cc: firstname.lastname@example.org <email@example.com>
Sent: Wed Jan 26 14:40:59 2011
Subject: Re: Failover Failure Advice
I currently have a Master/Slave Failover setup and I'm planning to deploy 100 ldap clients soon. I'm thinking about installing a Slave LDAP Server in all my ldap clients. I'm sure this will bog down the network but can I program syncrepl to be less chatty
between master and slave? I'm planning to point 60 of my clients to the master while the rest will point to the slave. Your thoughts?
On Tue, Jan 18, 2011 at 3:22 PM, jekvb <firstname.lastname@example.org>
On Tue, 2011-01-18 at 14:43 -0800, Anton Chu wrote:
My failover construction is a bit different, but it works quite nicely,
> I've setup a master and slave ldap service for failover;
so I 'd like to share this.
For a simple and reliable failover I have two LDAP servers in Mirror
mode with Keepalived on top of it. This is based on having one virtual
IP for both machines. When the one LDAP server (master) that has the IP,
fails, all read & write operations are directed to the backup server.
When the failed LDAP server comes up again it takes over the IP again
and SyncRepl on the slave takes care of updating the master.
Best regards, Kuba
This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.