Hello! slapd.conf configuration used *1.* I have test LDAP master and a consumer with LDAP Sync Replication type: Master: / overlay syncprov// // syncprov-checkpoint 100 10// // syncprov-sessionlog 100
/Consumer: syncrepl rid=115 provider=ldaps://master \ type=refreshOnly \ interval=00:00:00:30 \ scope=sub \ schemachecking=off \ searchbase="dc=exadel,dc=com" \ bindmethod=simple \ binddn="dc=exadel,dc=com" \ credentials=password \ retry="60 10 300 10" Sync is work.
*2.* After that I have switched to MirrorMode replication via reconfiguring Master and Consumer: Master1(Master): /serverID 1/ / overlay syncprov// // syncprov-checkpoint 100 10// // syncprov-sessionlog 100 / / syncrepl rid=001 provider=ldaps://Master2 // // bindmethod=simple // // interval=00:00:00:30 // // scope=sub // // binddn="dc=exadel,dc=com" // // credentials=password // // searchbase="dc=exadel,dc=com" // // schemachecking=off // // type=refreshOnly // // retry="60 +"// // // mirrormode on// / Master2(Consumer):
/serverID 2/ / overlay syncprov// // syncprov-checkpoint 100 10// // syncprov-sessionlog 100 / / syncrepl rid=002 provider=ldaps://Master1 // // bindmethod=simple // // interval=00:00:00:30 // // scope=sub // // binddn="dc=exadel,dc=com" // // credentials=password // // searchbase="dc=exadel,dc=com" // // schemachecking=off // // type=refreshOnly // // retry="60 +"// // // mirrormode on// / In this case SYNC is work(between Master1 -> Master2(NOT in Master2) -> Master1 direction) and other consumer pointed to Master1 or Master2)
*3.* For fun I change configuration on Master1(Master) to previous state(Case 1) Master1: / overlay syncprov// // syncprov-checkpoint 100 10// // syncprov-sessionlog 100
/ /Master2(Consumer):
/serverID 2/ / overlay syncprov// // syncprov-checkpoint 100 10// // syncprov-sessionlog 100 / / syncrepl rid=002 provider=ldaps://Master1 // // bindmethod=simple // // interval=00:00:00:30 // // scope=sub // // binddn="dc=exadel,dc=com" // // credentials=password // // searchbase="dc=exadel,dc=com" // // schemachecking=off // // type=refreshOnly // // retry="60 +"// // // mirrormode on//
//In this case we have the same situation with SYNC as in CASE 2 - all work fine.
Is it good working SYNC schema? What chance of breaking down db on Master1 I have?
--On Thursday, March 10, 2016 5:25 PM +0300 Andrei Valoshyn avaloshyn@exadel.com wrote:
In this case we have the same situation with SYNC as in CASE 2 - all work fine.
Is it good working SYNC schema? What chance of breaking down db on Master1 I have?
I'm not sure what your question is. Can you ellaborate?
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
Hello Quanah, The case 3 - not standard replication approuch for openldap. Kind of mix MirrorMode replication and LDAP Sync Replication. And I want to know - is this working solution in production? Will I face with some problems in future because non-standard type of replication?
On 3/10/2016 9:48 PM, Quanah Gibson-Mount wrote:
--On Thursday, March 10, 2016 5:25 PM +0300 Andrei Valoshyn avaloshyn@exadel.com wrote:
In this case we have the same situation with SYNC as in CASE 2 - all work fine.
Is it good working SYNC schema? What chance of breaking down db on Master1 I have?
I'm not sure what your question is. Can you ellaborate?
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc.
Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
--On Thursday, March 10, 2016 10:43 PM +0300 Andrei Valoshyn avaloshyn@exadel.com wrote:
Hello Quanah, The case 3 - not standard replication approuch for openldap. Kind of mix MirrorMode replication and LDAP Sync Replication. And I want to know - is this working solution in production? Will I face with some problems in future because non-standard type of replication?
I have no idea what you mean by that. "mirror mode" in OpenLDAP is simply multi-master replication (using ldap sync), where you use a load balancer to only ever direct writes to one specific master, and have the load balancer fail over to a different master if the one it is pointing at goes down.
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
--On Thursday, March 10, 2016 12:52 PM -0800 Quanah Gibson-Mount quanah@zimbra.com wrote:
--On Thursday, March 10, 2016 10:43 PM +0300 Andrei Valoshyn avaloshyn@exadel.com wrote:
Hello Quanah, The case 3 - not standard replication approuch for openldap. Kind of mix MirrorMode replication and LDAP Sync Replication. And I want to know - is this working solution in production? Will I face with some problems in future because non-standard type of replication?
I have no idea what you mean by that. "mirror mode" in OpenLDAP is simply multi-master replication (using ldap sync), where you use a load balancer to only ever direct writes to one specific master, and have the load balancer fail over to a different master if the one it is pointing at goes down.
You may wish to read http://www.openldap.org/doc/admin24/replication.html.
--Quanah
--
Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc
openldap-technical@openldap.org
-
Andrei Valoshyn -
Quanah Gibson-Mount