<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">On 08/25/2016 04:41 PM, bahan w wrote:<br>
</div>
<blockquote
cite="mid:CAMJtub+H2RewDB_vef17J9=3bthWs98=h-Ytm+xxiJNTUXjJ_w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div><br>
Hello everyone.<br>
<br>
</div>
Could you explain to me about this field Sent/Skipped please ?<br>
</div>
</div>
</blockquote>
if replication is enabled all changes on a server are logged into
the changelog -changes coming from clients and internal changes (eg
mmeberof update, passwordpolocy updates, lstlogin time ...).<br>
In the replication agreement you can configure attributes for which
changes are not replicated (keep them local) - and IPA uses this
feature eg for krblastlogintime.<br>
<br>
Looking at the replication traffic your monitoring shows, I think
most of the "real" updates are going to one server and most of the
clients triggering internal updates are going to the other. This
makes replciation in one direction "normal" and in the other
fractional. The problem with fractional is that the determined
staring point for a replciation session can b every far behind and
it again and again iterates over the same changes until finally an
update which is not skipped is found.<br>
<br>
There are some options to improve this:<br>
- upgarde to a newer version, teh DS will automatically generate
updates to a "keep alive" entry, so that the sequences of skipped
changes get much smaller<br>
- do it yourself by regularily applying a dummy update on the
problematic server which will be replicated <br>
- check configuration if writing the internal mods can be avoided, I
think there is an option not to log krblastlogin<br>
<br>
<blockquote
cite="mid:CAMJtub+H2RewDB_vef17J9=3bthWs98=h-Ytm+xxiJNTUXjJ_w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>I checked the doc and found this :<br>
###<br>
<table class="" style="mso-cellspacing:1.5pt;
mso-yfti-tbllook:1184;mso-padding-alt:0cm 0cm 0cm 0cm"
border="0" cellpadding="0">
<tbody>
<tr
style="mso-yfti-irow:0;mso-yfti-firstrow:yes;mso-yfti-lastrow:yes">
<td style="padding:0.75pt">
<p class="MsoNormal">Sent/Skipped :<br>
</p>
</td>
<td style="padding:0.75pt">
<p class="MsoNormal">The number of changes that were
sent from the supplier and the number skipped in the
replication update. The numbers are kept in
suppliers’ memory only and are cleared if the
supplier is restarted.</p>
</td>
</tr>
</tbody>
</table>
###<br>
<br>
</div>
<div>If I check the first part :<br>
###<br>
<span class="im">Master: <MASTER OK>:389
<a class="moz-txt-link-freetext" href="ldap://">ldap://</a><MASTER OK>:389/<br>
Replica ID: 4<br>
Replica Root: dc=<REALM><br>
</span>Max CSN: 57bdcd36000100040000 (08/24/2016 18:37:10 1 0)<br>
Receiver: <MASTER UNSYNC>:389 <a class="moz-txt-link-freetext" href="ldap://">ldap://</a><MASTER
UNSYNC>:389/<span class="im"><br>
Type: master<br>
Time Lag: 0:00:00<br>
</span>Max CSN: 57bdcd36000100040000 (08/24/2016 18:37:10 1 0)<br>
Last Modify Time: 8/24/2016 18:36:32<br>
Supplier: <MASTER OK>:389<br>
Sent/Skipped: 182110 / 1054<span class="im"><br>
Update Status: 0 Replica acquired successfully: Incremental
update succeeded<br>
</span>Update Started: 08/24/2016 18:36:32<br>
Update Ended: 08/24/2016 18:36:34<span class="im"><br>
Schedule: always in sync<br>
SSL: SASL/GSSAPI<br>
###<br>
<br>
</span></div>
<div><span class="im">This is the replication from the MASTER OK
(the supplier) to the MASTER UNSYNC (the receiver), right ?<br>
</span></div>
<div><span class="im">So, the MASTER OK sent 182110 changes.<br>
</span></div>
<div><span class="im">And in addition to these 182110 changes,
1054 changes were sent to the MASTER UNSYNC but skipped by
the MASTER UNSYNC, right ?<br>
</span></div>
<div><span class="im">Why are they skipped ?<br>
<br>
</span></div>
<div><span class="im">In the other side, if I take the second
part :<br>
###<br>
</span><span class="im">Master: <MASTER UNSYNC>:389
<a class="moz-txt-link-freetext" href="ldap://">ldap://</a><MASTER UNSYNC>:389/<span class="im"><br>
Replica ID: 3<br>
Replica Root: dc=<REALM><br>
Max CSN: 57bdbda1000000030000 (08/24/2016 17:30:41)<br>
Receiver: <MASTER OK>:389 <a class="moz-txt-link-freetext" href="ldap://">ldap://</a><MASTER
OK>:389/<br>
Type: master<br>
Time Lag: - 0:22:29<br>
Max CSN: 57bdb85c000000030000 (08/24/2016 17:08:12)<br>
Last Modify Time: 8/24/2016 17:07:34<br>
</span>Supplier: <MASTER UNSYNC>:389<br>
Sent/Skipped: 3 / 9048655<span class="im"><br>
Update Status: 0 Replica acquired successfully:
Incremental update succeeded<br>
</span>Update Started: 08/24/2016 18:36:33<br>
Update Ended: 08/24/2016 18:36:34<span class="im"><br>
Schedule: always in sync<br>
SSL: SASL/GSSAPI</span><br>
###<br>
<br>
</span></div>
<div><span class="im">The supplier is the MASTER UNSYNC and the
receiver is the MASTER OK.<br>
</span></div>
<div><span class="im">In this case I have only 3 changes sent.<br>
</span></div>
<div><span class="im">And in addition to these 3 changes, 9 048
655 changes were sent but skipped on the MASTER OK, right ?<br>
<br>
</span></div>
<div><span class="im">I ask these questions just to be sure I
understand right the return of the pl script.<br>
</span></div>
<div><span class="im"></span></div>
<div><span class="im"></span></div>
<div><br>
</div>
<div><br>
</div>
<div class="gmail_extra">Best regards.<br>
<br>
</div>
<div class="gmail_extra">Bahan<br>
</div>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Red Hat GmbH, <a class="moz-txt-link-freetext" href="http://www.de.redhat.com/">http://www.de.redhat.com/</a>, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander</pre>
</body>
</html>