8:01 a.m.
Hi all,
A directory is configured as delta-syncrepl provider, the backends for the
main database and the accesslog database are both mdb. Everything works
fine, my question is: What happens if there are so many write ops that the
size of the accesslog database reaches the value of olcDbMaxSize defined
for this database? Thanks!
Cheers,
Manuela
8:24 a.m.
--On Tuesday, May 14, 2019 6:01 PM +0200 Manuela Mandache
<manuela.mandache.mm(a)gmail.com> wrote:
Hi all,
A directory is configured as delta-syncrepl provider, the backends for
the main database and the accesslog database are both mdb. Everything
works fine, my question is: What happens if there are so many write ops
that the size of the accesslog database reaches the value of olcDbMaxSize
defined for this database? Thanks!
Replication will grind to a halt. Generally one should set the maxsize of
an MDB database to a very large value such that this situation should not
be encountered.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
10:03 a.m.
Manuela Mandache <manuela.mandache.mm(a)gmail.com> writes:
Hi all,
A directory is configured as delta-syncrepl provider, the backends for
the main database and the accesslog database are both mdb. Everything
works fine, my question is: What happens if there are so many write
ops that the size of the accesslog database reaches the value of
olcDbMaxSize defined for this database? Thanks!
Depending on the number of operations you may set logpurge to a
appropriate value.
-Dieter
--
Dieter Klünter | Systemberatung
http://sys4.de
GPG Key ID: E9ED159B
53°37'09,95"N
10°08'02,42"E
10:31 a.m.
--On Tuesday, May 14, 2019 8:03 PM +0200 Dieter Kluenter
<dieter(a)dkluenter.de> wrote:
> olcDbMaxSize defined for this database? Thanks!
Depending on the number of operations you may set logpurge to a
appropriate value.
Yeah, I think the question is, what happens if you have so many operations
in an <interval> that it maxes out the DB, where the interval is smaller
than the logpurge interval. But it's a good point, one could (if using
cn=config) do an on-the-fly modification of the logpurge interval so that
the DB gets purged more frequently to accomodate the rate of change.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
1596
days inactive
1596
days old
openldap-technical@openldap.org
3 comments
3 participants
participants (3)
-
Dieter Kluenter -
Manuela Mandache -
Quanah Gibson-Mount