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

Re: (ITS#4626) "glue" objectclass in syncrepl consumer

ahasenack@terra.com.br wrote:
> On Fri, Sep 22, 2006 at 07:48:33PM +0000, hyc@symas.com wrote:
>> Yes, this makes sense.
>> Since all of the CSNs under ou=global are greater than any CSN under 
>> dc=example,dc=com, none of those entries are sent. In server B your 
>> consumer should be configured on dc=example,dc=com, with a searchbase of 
>> ou=global,dc=example,dc=com. That will allow the server B provider to 
>> stay in sync with its consumer.
> With this change, the replication is better, but the B server cannot be
> written to anymore: moving the syncrepl directive to the
> dc=example,dc=com database makes it read-only because it is then
> considered a consumer.

This portion of your report is the same as ITS#4623. The fix for ITS#4623 is 
in HEAD and probably will only be in 2.4. The other part of the problem, 
where objects get turned into glue objects, is fixed by ITS#4813. This fix is 
in RE23 and will be in 2.3.34. I'm closing this ITS, you can followup to 
#4623 or #4813 if you need to make any further comments.

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