<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/30/2015 03:54 PM, Ludwig Krispenz
wrote:<br>
</div>
<blockquote cite="mid:55929F86.6010907@redhat.com" type="cite">Hi,
<br>
<br>
389-ds allows to configure the max size of the replication
changelog either by setting a maximum record number or a maximum
age of changes.
<br>
freeIPA does not use this setting. In the context of ticket
<a class="moz-txt-link-freetext" href="https://fedorahosted.org/freeipa/ticket/5086">https://fedorahosted.org/freeipa/ticket/5086</a> we are discussing to
change the default to
<br>
enable changelog trimming.
<br>
<br>
Does anyone already use changlog trimming or is there a scenario
where you rely on all changes being available ?
<br>
<br>
Thanks for your feedback,
<br>
Ludwig
<br>
<br>
</blockquote>
<font face="Times New Roman, Times, serif">Hello,<br>
<br>
</font>
<blockquote><font face="Times New Roman, Times, serif">I think it is
reasonable to set nsds5ReplicaPurgeDelay and
nsslapd-changelogmaxage to similar value.<br>
<br>
When a replica (master or consumer) is down for some time and is
restarted, both attribute express the ability to get the replica
in sync with the rest of the topology.<br>
It can work (and likely will) if </font><font face="Times New
Roman, Times, serif"><font face="Times New Roman, Times, serif">nsds5ReplicaPurgeDelay<</font></font><font
face="Times New Roman, Times, serif">nsslapd-changelogmaxage but
there are always corner cases that can lead to problem (like
entries that diverge).<br>
<br>
Currently purgedelay=7days (default) and changelogmaxage is
infinite and changing purgedelay=infinite impacts the size of
the entries.<br>
<br>
thanks<br>
thierry<br>
<br>
<br>
<br>
</font></blockquote>
</body>
</html>