From c08575b5d155b34529c402d7e5398e77abc49117 Mon Sep 17 00:00:00 2001
From: gbellato <gbellato@localhost>
Date: Mon, 20 Aug 2007 08:04:16 +0000
Subject: [PATCH] These changes rovides the ability to repair the consistency in the replication topology in the (hopefully) rare case when hardware failure or software bugs could break it (issue 788 and 791)
---
opends/src/server/org/opends/server/replication/plugin/Historical.java | 19 +++++--------------
1 files changed, 5 insertions(+), 14 deletions(-)
diff --git a/opends/src/server/org/opends/server/replication/plugin/Historical.java b/opends/src/server/org/opends/server/replication/plugin/Historical.java
index f2c4f8a..2912126 100644
--- a/opends/src/server/org/opends/server/replication/plugin/Historical.java
+++ b/opends/src/server/org/opends/server/replication/plugin/Historical.java
@@ -374,8 +374,11 @@
* This attribute is unknown from the schema
* Just skip it, the modification will be processed but no
* historical information is going to be kept.
- * TODO : REPAIR tool should deal with this, add some logging.
+ * Log information for the repair tool.
*/
+ Message message = ERR_UNKNOWN_ATTRIBUTE_IN_HISTORICAL.get(
+ entry.getDN().toNormalizedString(), histVal.getAttrString());
+ logError(message);
continue;
}
@@ -453,19 +456,7 @@
if (fakeOperation != null)
{
- try
- {
- fakeOperation.addModification(mod);
- } catch (Exception e)
- {
- /*
- * TODO : REPAIR : This Exception shows that there are some
- * inconsistency in the historical information.
- * This method can't fix the problem.
- * This should be logged and somehow the repair
- * service should get called to fix the problem.
- */
- }
+ fakeOperation.addModification(mod);
}
else
{
--
Gitblit v1.10.0