[OPENDS-2424] impact of generation ID on binary copy Created: 05/Oct/07
Updated:
19/Feb/08 Resolved: 19/Feb/08
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Environment:
Issuezilla Id:
Tags:
Resolved
opends
Replication
pre-1.0
1.0
Task
gbellato
Fixed
None
Not Specified
Priority:
Assignee:
Votes:
Major
pgamba
0
Not Specified
Not Specified
Operating System: All
Platform: All
URL:
https://www.opends.org/wiki/page/HowToInitializeAReplicatedServerWithData
2,424
doc_complete
Description
Because the replication server keeps the generation ID and only accept
provide its service to LDAP servers with the same generation ID
copying the database through a binary copy might not always be enought
for reinitializing the replication in a topology :
If a replication have kept an old generation ID, then it will not take
part in the replication.
If all replication servers still have old generation IDs then the
replication will not work at all.
The replication currently provides a task that allow to reset the generation ID
in the replication servers. This should somehow be made available in the admin
tools.
Comments
Comment by gbellato [ 22/Oct/07 ]
After discussion with Philippe we decided that :


All the scenario of binary copy already
works when the server are new servers
When a user wants to reuse a topology with new data we will to require
to first disable replication on all servers so that the replication
server database are cleaned
Therefore there is no need for a public way to invoke the reset generation ID
task.
Comment by pgamba [ 14/Nov/07 ]
svn commit -m "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"
Sending resource/schema/02-config.ldif
Sending src/messages/messages/task.properties
Sending src/server/org/opends/server/config/ConfigConstants.java
Sending
src/server/org/opends/server/replication/plugin/ReplicationDomain.java
Sending src/server/org/opends/server/tasks/SetGenerationIdTask.java
Sending
tests/unit-tests-testng/src/server/org/opends/server/replication/GenerationIdTest.java
Transmitting file data ......
Committed revision 3452.
Comment by pgamba [ 15/Nov/07 ]
svn commit -m "Fix #2424 impact of generation ID on binary copy - an LDAP
server that has already sent changes must not be able to replicate with an empty
replication server"
Sending src/server/org/opends/server/replication/common/ServerState.java
Sending src/server/org/opends/server/replication/server/ServerHandler.java
Transmitting file data ..
Committed revision 3454.
Comment by jvergara [ 15/Nov/07 ]
The following subcommands have been added to dsreplicaton in revision 3455:
Usage:
$ dsreplication pre-external-initialization --help
dsreplication pre-external-initialization
{options}
This subcommand must be called before initializing the contents of all the
replicated servers using the tool import-ldif or the binary copy method for
replication to work. You must specify the list of Base DNs that will be
initialized and you must provide the credentials of any of the servers that is
being replicated. After calling this subcommand, you must initialize the
contents of all the servers in the topology and after the initialization is over
you must call the subcommand {post-external-initialization}.
Global Options: See "dsreplication --help"
SubCommand Options:
-h, --hostname {host}
Directory server hostname or IP address
-p, --port {port}
Directory server port number
-Z, --useSSL
Use SSL for secure communication with the server
-q, --useStartTLS
Use StartTLS to secure communication with the server
-l, --only-local
Use this option when only the contents of the specified directory server
will be initialized with an external method (import-ldif command or binary copy)
$ dsreplication post-external-initialization --help
Usage: dsreplication post-external-initialization {options}
This subcommand must be called after initializing the contents of all the
replicated servers using the tool import-ldif or the binary copy method for
replication to work. You must specify the list of Base DNs that have been
initialized and you must provide the credentials of any of the servers that is
being replicated. See the usage of the subcommand
{pre-external-initialization}
for more information.
Global Options:
See "dsreplication --help"
SubCommand Options:
-h, --hostname
{host}
Directory server hostname or IP address
-p, --port
{port}
Directory server port number
-Z, --useSSL
Use SSL for secure communication with the server
-q, --useStartTLS
Use StartTLS to secure communication with the server
Comment by pgamba [ 14/Feb/08 ]
Feature documented at
https://www.opends.org/wiki/page/HowToInitializeAReplicatedServerWithData
Generated at Tue Feb 09 11:22:39 UTC 2016 using JIRA 6.2.3#6260sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.