[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openldap-devel
Subject:    Re: replicate internal operations
From:       Howard Chu <hyc () symas ! com>
Date:       2011-05-25 15:15:57
Message-ID: 4DDD1D2D.50809 () symas ! com
[Download RAW message or body]

Michael Ströder wrote:
> Taking this to -devel for clarification.
>
> hyc@symas.com wrote:
>> The original design for memberOf was for the internal modifications to not be
>> replicated. Instead, any replicas that wanted to maintain member information
>> was expected to run an identical memberOf overlay configuration.
>
> Ok.
>
>> In general it's incorrect to replicate internal operations. The fanout from
>> replicating every internal operation would be too large and the information
>> content of what is being replicated is essentially nil. When the servers are
>> configured identically they will maintain identical data by virtue of the
>> overlays on each node performing the same internal operations in response to a
>> given sequence of user operations.
>
> While I agree here I think "internal operations" has to be defined a little
> bit more clear: What about extended operations which may result in several
> write operations? Extended operations are not written to the accesslog-DB and
> are not replicated.

An internal operation is any op that was not received from some LDAP client by 
the slapd frontend. The accesslog overlay supports extended operations. If you 
know of an exop that isn't being logged but ought to be, that's a separate bug 
that you should report.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/

[prev in list] [next in list] [prev in thread] [next in thread]