From b9aad30c9e07b179a2c22fad830f6a54b8993bc9 Mon Sep 17 00:00:00 2001
From: ludovicp <ludovicp@localhost>
Date: Wed, 18 Aug 2010 13:27:32 +0000
Subject: [PATCH] First pass on solving issue #514, reducing Replication meta data, especially aged information. The default is to keep the replication meta data (historical information) for at least 1 day. Purging occurs on the fly when entries are modified, or via a task. Launching the task will be available through dsreplication in separate commit.
---
opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml | 22 ++++++++++++++++++++++
1 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml b/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml
index 1bc7968..95aafdc 100644
--- a/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml
+++ b/opends/src/admin/defn/org/opends/server/admin/std/ReplicationDomainConfiguration.xml
@@ -536,4 +536,26 @@
</ldap:attribute>
</adm:profile>
</adm:property>
+ <adm:property name="conflicts-historical-purge-delay">
+ <adm:synopsis>
+ This delay indicates the time (in minutes) the domain keeps the historical
+ information necessary to solve conflicts.When a change stored in the
+ historical part of the user entry has a date (from its replication ChangeNumber)
+ older than this delay, it is candidate to be purged.
+ The purge is applied on 2 events: modify of the entry, dedicated purge task.
+ </adm:synopsis>
+ <adm:default-behavior>
+ <adm:defined>
+ <adm:value>1440m</adm:value>
+ </adm:defined>
+ </adm:default-behavior>
+ <adm:syntax>
+ <adm:duration base-unit="m" allow-unlimited="false" />
+ </adm:syntax>
+ <adm:profile name="ldap">
+ <ldap:attribute>
+ <ldap:name>ds-cfg-conflicts-historical-purge-delay</ldap:name>
+ </ldap:attribute>
+ </adm:profile>
+ </adm:property>
</adm:managed-object>
--
Gitblit v1.10.0