We don't have load balancers yet, but we have cross site replicas that suffers many client reconnecting when one side is failing and are considering adding both replicas and lb in front.
Thanks for the point. ________________________________ De : chris.paul@rexconsulting.net chris.paul@rexconsulting.net Envoyé : samedi 30 mars 2024 16:36 À : openldap-technical openldap-technical@openldap.org Objet : Re: Help debugging slave slapd issues
[Vous ne recevez pas souvent de courriers de chris.paul@rexconsulting.net. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ]
ATTENTION : Cet e-mail provient de l'extérieur de l'organisation. Ne cliquez pas sur les liens et n'ouvrez pas les pièces jointes à moins que vous ne reconnaissiez l'expéditeur et que vous sachiez que le contenu est sûr.
On 3/25/24 12:52 PM, Howard Chu hyc@symas.com wrote:
Yes, they're common, and these are caused by a client sending too many operations over a connection without waiting for them to complete. In other words, a poorly written client.
Simply adding more replicas does nothing to address this, you need a load balancer that spreads all client queries out, even when they're all coming in from a single connection.
Better yet is to identify the client and fix it.
I won't disagree with Howard, who knows a lot more than I do about OpenLDAP.
But I do want to add that if you do have a load balancer, and you do see these, then check if your load balancer is using SNAT to manage client connections. Usually load balancers do use SNAT.
In the case you see these errors and you are using load balancers that SNAT client IPs, then adding replicas is a good fix.
Chris Paul | https://www.rexconsulting.net