|
On 12/23/2015 11:16 AM, bahan w wrote:
Simple description: When a replica is updated by a client, that "update" goes into the replication changelog. Then each replication agreement reads the change log and sends those updates to the replication consumer defined in the agreement. Then the process continues on each replica until the change is present in all the servers. There's much more to it than that, but that's the basic idea Each replica has/creates its own "keep alive" entry. It's the replica ID https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/Managing_Replication-Configuring_Multi_Master_Replication.html#Multi_Master_Replication-Configuring_the_Read_Write_Replicas_on_the_Supplier_Servers If a replica is not directly updated in a long time then the last changes it received from a client can get purged from the changelog and/or entry meta data. Which makes it impossible to update other replicas once this condition is hit. This is more prevalent when using fractional replication(which ipa uses). This is a very complicated process, and out of the scope of this discussion. You don't need to worry about this entry :-) And the error message you reported is actually just a information message - it should be changed to a different log level.
Doesn't hesitate to look at the docs: https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10/html/Administration_Guide/Managing_Replication.html And our wiki has some great content: http://ww.port389.org Mark
|
-- 389 users mailing list 389-users@%(host_name)s http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
