[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#5694) Usage of -w with slapadd breaks delta-syncrepl

Quanah Gibson-Mount wrote:
> --On Tuesday, September 09, 2008 8:50 PM +0200 Pierangelo Masarati 
> <ando@sys-net.it> wrote:
>> I thuink the issue is related to the fact that slapadd -w uses
>> bi_tool_entry_modify() and bi_tool_sync().  However, slapo-accesslog(5)
>> does not implement those hooks.  As a consequence, any modification to
>> the context entry is not reflected in slapo-accesslog(5).
>> However, I don't see how this should affect replication, since a
>> consistent database, after slapcatt'ing, should generate a ldif with the
>> correct contextCSN.  However, if you slapcat before stopping the
>> producer, the resulting ldif will not contain the contextCSN, because
>> after a fresh slapadd without -w it's kept in memory until the producer
>> is stopped.  You should try
> It should be possible to restore a working provider/slave relationship 
> from a hot slapcat taken at any point in time.

Well, actually slapadd -w should suffice.  As an alternative, slapcat 
could support -w as well, for symmetry, so that consistent ldifs can be 

> I'll give what you suggested a try, but this is still a serious bug.

There's something I don't clearly get.  As far as I understand, you are 
saying that consumers lose sync when the log database is purged before 
they have a chance to sync (because they were down).  I don't see how 
they could sync, then.  Of course, there should be a means for 
slapo-syncprov(5) to tell that, and force a refresh.


Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Fax:     +39 0382 476497
Email:   ando@sys-net.it