On 10/29/2013 07:39 PM, Quanah Gibson-Mount wrote:
--On Tuesday, October 29, 2013 5:56 PM +0100 Patrick Lists openldap-list@puzzled.xs4all.nl wrote:
Now if I understand that multi-master config example in the Admin Guide correctly (see link above) it should also be possible to use this config:
ldap01: config with cn=config + syncprov & accesslog overlays and the main mdb + syncprov & accesslog overlays. Both with olcMirrorMode: TRUE
ldap02: config with cn=config + syncprov & accesslog overlays with olcMirrorMode: TRUE
And when ldap02 is started it should sync the entire config from ldap01 (including the main database) and also replicate the data in the main database. At least that is how I read the sentence "We still have to replicate the actual data, not just the config, so add to the master (all active and configured consumers/masters will pull down this config, as they are all syncing)". Is my interpretation correct?
No idea... as I said, I've never set up cn=config replication, and I've never run with mismatched configurations for MMR. Clearly ldap02's config for the primary db doesn't match, so I would hope it would work? I'd say test and report back. ;)
I guess I should have mentioned that I tested it with mismatched delta-syncrepl multi-master configs and it did not work. All I saw was ldap01's cn=config replicate to ldap02 but not the main database. And ldap01 was complaining that it could not reach the rid of the main database on ldap02 which makes sense. Would be cool if this worked though.
Regards, Patrick