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

Re: Syncrepl of portions of glued database - problems (in HEAD)

Pierangelo Masarati wrote:

Pierangelo Masarati wrote:

Pierangelo Masarati wrote:

However, further updates are not sync'ed; same with refreshOnly.

Let me add that 2.2 works fine.

I think the problem is that both the "glue" and the "syncprov" overlays, when running searches, set

   op->o_bd->bd_info = on->on_info->oi_orig

so that further overlays in the stack are not invoked. Regardless of the order the overlays are stacked, either "findbase failed! 32" when syncprov is executed first (i.e. configured last) or the syncprov overlay is not invoked when glue is executed first (i.e. configured last). In any case, overlays need be stacked at the glue database, because those at the subordinate databases seem to be plainly ignored. I think the glue overlay should account either for other overlays stacked at the glue database or for overlays stacked at each subrodinate database, or better both.

The above analysis is partly wrong. The glue overlay correctly calls the per-database stack of overlays. The point is that the syncprov overlay in the glue database is needed only to advertize support for LDAP Sync; I think a better approach is to make the glue database inherit the controls supported by the subordinate databases. And it's definitely time to move this discussion to -devel; please reply there, in case.


   SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497