On Tue, 8 Oct 2013, Michael Ströder wrote:
I don't want to keep you away from contributing this but you
should be aware
of two issues:
1. You have much higher load because of the chaining to a provider and
subsequent replication to the consumers.
2. If the provider is down slapo-ppolicy does *not* write any ppolicy
attributes at all.
I whipped up following patch and would like some review on it:
The patch introduces a new lastbind_forward_updates (olcLastBindForwardUpdates )
boolean parameter to slapo-lastbind that has the same semantics as
ppolicy_forward_updates (olcPPolicyForwardUpdates) in slapo-ppolicy.
I adapted the code from slapo-ppolicy but was not sure of one line I
marked with TODO in the patch.
I have a 2 master, 2 slave syncrepl test setup which chaining from
the slaves to the masters ( to one of them to be precise ).
- Bind on master1 results in authTimestamp getting replicated to master2
and both slaves.
- Bind on slave1 with olcLastBindForwardUpdates=TRUE results in authTimestamp
getting forwarded to the master with updateRef and chaining and replicated
I have also patch the slapo-lastbind.5 manpage.
This of course needs a review before being used in production.
Christian Kratzer CK Software GmbH
Email: ck(a)cksoft.de Wildberger Weg 24/2
Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden
Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart
Geschaeftsfuehrer: Christian Kratzer