N-Way multi-master configuration

To: openldap-technical@openldap.org

Subject: N-Way multi-master configuration

From: Dave Lambley <dave.lambley@gmail.com>

Date: Wed, 28 Jun 2017 22:25:50 +0100

Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:to; bh=N+uor/QXoO1cqJLTd3s39+VdwTAwZ8uj7poXUBPqe5U=; b=jWqui2eYhljXL8Cp6hGQB4ZYrIcJcYiFQ2vxjfuda5oz2GPD692JTV6XipJibHYroB SMy5YqoVbg4dmqM67aMLiUJOufIfUCz1FzRS6onOqQ927P0AfdflLUPTleCMbmFzdDSu iHXZ0M2eP23ngZ7rYcy1CilQPfysvGi7rzyOaCBBJG6iUTCw+3mwbLelFMXuJBwNb6D0 86FZ2MiOWTRGRDR31oFEyZXnYWMEjCeFx/fwcpsc/R0gZ6YPl/CkJ0bkHSWPvehbSeRd jzDwT2Fm8GztmahHUYntPE91JH8gIr2NhfzRrBTl5BVVoMcywMqpG+JF2RDFOVTa3LhA GjSw==

We are using OpenLDAP 2.4.31 under Ubuntu 14.04, doing four way multi master replication. When I initially configured it, I set the data (as opposed to config) replication to be "type=refreshOnly", as described here, http://www.openldap.org/doc/admin24/replication.html#N-Way%20Multi-Master

That didn't work well, we lost insertions and and memory usage of some servers steadily over the two weeks I left it. Switching the replication to "type=refreshAndPersist" resolved both problems.

What is the reason the documentation suggests "type=refreshOnly" for data, but not for config? Should I expect any problems using "type=refreshAndPersist" for data?

Best regards,

Dave Lambley