Hey,
I have, what I hope is, a vanilla mirror-master setup,
There is a load balancer in between the providers and consumers, that ensures that the writes will consistently be written to a single provider, until it becomes unavailable - at which point writes will failover to the hot-stand by.
With regards to replication for the consumers - currently they all have a single provider explicitly defined within their configuration and I'm trying to understand what options are available with which the failover from one provider to the other would best be handled if the master was to die?
I realise that the RID has to be unique - so am I right in thinking that there is no way for the failover to seamless, and replication must be re-established by removing the existing syncrepl statement, on the consumers, and re-adding it with the secondaries details?
Or am I missing a trick here as to how the process could be smoother?
Thanks in advance
Today at 7:43am, Tim wrote:
I realise that the RID has to be unique - so am I right in thinking that there is no way for the failover to seamless, and replication must be re-established by removing the existing syncrepl statement, on the consumers, and re-adding it with the secondaries details?
Or am I missing a trick here as to how the process could be smoother?
You are missing the point.
You say you have a load balancer that decides which of your MMR partners should receive the traffic. Your consumers should be configured in such a way that both MMR partners will accept the connection.
For example...
My MMR partners are ldap7p and ldap7q. The load balanced VIP is ldap7rw. My consumers are set up with unique RIDs (the RID is unique for each consumer) and their provider is ldap7rw. It does not matter whether the load balancer sends the traffic to ldap7p or ldap7q - the consumer is talking to ldap7rw.
openldap-technical@openldap.org