Red Hat Directory Server 8.0 Administrator's Guide
Table Description
supplier replica, the replica root, and the
maximum Change State Number (CSN) on
the supplier. The important thing is to make
sure that each supplier LDAP server has its
unique replica ID. Multiple replica roots on
one LDAP server, however, could share the
same replica ID.
Table Row Each row represents a direct or indirect
consumer of the supplier (identified in the
Table Header).
Max CSN It is the most recent CSN the consumer has
replayed that was originated from the supplier
(identified in the Table Header).
Time Lag It shows the time difference between the
supplier and the consumer's max CSNs for
the changes originated from the supplier
(identified in the Table Header). A consumer
is in sync with its supplier when its time lag is
0.
Last Modify Time It is roughly the time when the consumer's
max CSN was replayed.
Supplier This column lists all the suppliers of the
consumer.
Sent/Skipped Each supplier lists roughly how many
changes originated from the supplier
(identified in the Table Header) have been
replayed or skipped by the consumer. The
numbers are kept in suppliers' memory only.
They will be cleared if the supplier is
restarted.
Update Status The number is the status code, and the string
is the implication of the status code. Watch
this column for possible deadlock if all the
suppliers complain that they cannot acquire
the busy replica. It is normal if one of the
suppliers is doing an update while the others
can't acquire the busy replica.
18. Solving Common Replication Conflicts
Multi-master replication uses a loose consistency replication model. This means that the same
entries can be changed on different servers. When replication occurs between the two servers,
Chapter 8. Managing Replication
342