[Date Prev][Date Next]
Re: (ITS#3724) back_meta more sizelimit problems
> On Fri, 2005-05-13 at 12:11 +0200, Pierangelo Masarati wrote:
>> > These tests were applied to 2.2.23 with the patch from its#3720.
>> Could you please check if the same problem, or different problems occur
>> without the patch, i.e. if there's any regression issue?
never mind, I've got it.
> I've done this and the behaviour is the same. No regression issues.
>> I'll try to reproduce the issue; I fear a conflict between back-meta and
>> backglue sizelimit handling.
Indeed there's a conflict: backglue decreases the enforced sizelimit by
the amount of entries returned by each subordinate database, so back-meta
sees a sizelimit of 1 when it is after the bdb and the bdb returns one
entry; but back-meta uses the overal entry count to check if the sizelimit
has been exceeded. I need to use a local count. A fix is about to come.
Thanks for reporting.
By the way, let me note that glueing a back-meta with a local database may
not be a good choice because backglue performs operations searially, while
back-meta perofrms them in parallel; if the remoter server response is
orders of magnitude slower than that of the local database, you may want
to turn the subordinate bdb into an additional target of the back-meta,
possibly using a ldapi:// listener, so that operations are run in parallel
on all databases, and the performance penalty of the remote servers is
spread across all the operation time.
SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497