From 110726757d33bae25fabde2a8dbd2d9203e85526 Mon Sep 17 00:00:00 2001
From: pgamba <pgamba@localhost>
Date: Wed, 14 Nov 2007 18:20:29 +0000
Subject: [PATCH] Fix 2424 - impact of generation ID on binary copy - add to the SetGenerationID task the possibility to clear the generation id in the topology by providing the attribute ds-task-reset-generation-id-new-value with value -1
---
opends/src/server/org/opends/server/replication/plugin/ReplicationDomain.java | 14 ++++++++++++--
1 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/opends/src/server/org/opends/server/replication/plugin/ReplicationDomain.java b/opends/src/server/org/opends/server/replication/plugin/ReplicationDomain.java
index 462d4b2..1422ef8 100644
--- a/opends/src/server/org/opends/server/replication/plugin/ReplicationDomain.java
+++ b/opends/src/server/org/opends/server/replication/plugin/ReplicationDomain.java
@@ -2517,11 +2517,21 @@
* Reset the generationId of this domain in the whole topology.
* A message is sent to the Replication Servers for them to reset
* their change dbs.
+ *
+ * @param generationIdNewValue The new value of the generation Id.
*/
- public void resetGenerationId()
+ public void resetGenerationId(Long generationIdNewValue)
{
+ ResetGenerationId genIdMessage = null;
requestedResetSinceLastStart = true;
- ResetGenerationId genIdMessage = new ResetGenerationId(this.generationId);
+ if (generationIdNewValue == null)
+ {
+ genIdMessage = new ResetGenerationId(this.generationId);
+ }
+ else
+ {
+ genIdMessage = new ResetGenerationId(generationIdNewValue);
+ }
broker.publish(genIdMessage);
}
--
Gitblit v1.10.0