[OPENDJ-282] dsreplication enable fails with duplicate server ID, while it's
about the same server being referenced. Created: 14/Sep/11 Updated: 15/Feb/13 Resolved: 14/Sep/11
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Testing
OpenDJ
replication
2.4.3
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Bug
Ludo Poitou
Fixed
release-notes
Not Specified
Case Id:
EYL-479216
2.4.4, 2.6.0
Priority:
Assignee:
Votes:
Major
Ludo Poitou
0
Not Specified
Not Specified
Description
Issue raised by a customer:
Merging registration information .....
The following servers in the two topologies have the same replication server
ID
Server ds14.example.com:4444 and server
ds14.example.com:4444 have the same replication server ID: 8268.
The replication topologies cannot be merged. To fix this problem please refer
to the documentation.
See /tmp/opends-replication-2602220733558064475.log for a detailed log of this
operation.
And the log contains:
SEVERE: Complete error stack:
org.opends.server.tools.dsreplication.ReplicationCliException: The following servers in the two topologies
have the same replication server ID
Server ds14.example.com:4444 and server ds14.example.com:4444 have the same replication server ID:
8268.
The replication topologies cannot be merged. To fix this problem please refer to the documentation.
at org.opends.server.tools.dsreplication.ReplicationCliMain.mergeRegistries(ReplicationCliMain.java:11240)
at
org.opends.server.tools.dsreplication.ReplicationCliMain.updateConfiguration(ReplicationCliMain.java:5994)
at org.opends.server.tools.dsreplication.ReplicationCliMain.enableReplication(ReplicationCliMain.java:4343)
at org.opends.server.tools.dsreplication.ReplicationCliMain.enableReplication(ReplicationCliMain.java:663)
at org.opends.server.tools.dsreplication.ReplicationCliMain.execute(ReplicationCliMain.java:480)
at org.opends.server.tools.dsreplication.ReplicationCliMain.mainCLI(ReplicationCliMain.java:352)
at org.opends.server.tools.dsreplication.ReplicationCliMain.main(ReplicationCliMain.java:283)
Comments
Comment by Ludo Poitou [ 14/Sep/11 ]
Customer configuration includes 2 servers that are both DS and RS and many others that are just
DS.
The disabled server is one of the 2 main (DS & RS) but only DS replication service was
disabled.
I did not manage to reproduce the issue with a test environment including 4 servers.
Comment by Ludo Poitou [ 14/Sep/11 ]
Resolved in both b2.4 branch and trunk
Comment by bsegonnes [ 28/Nov/11 ]
Hi,
I have the same issue (even if server Id are different on both replicated server logs), the error
message say they are the same.
Those 2.4.3 servers are used in Production environment. It will be difficult (long
qualification/tests/validation process) to upgrade to 2.4.4
Is there a workaround ? Could restarting one server help ?
Comment by Ludo Poitou [ 28/Nov/11 ]
Hi,
Unfortunately, the issue lies in some code used when initializing replicas and is not related to
the server's process.
Restarting servers will not help.
I can't think of any workaround to it, other than completely disabling replication on all servers,
and re-enabling it. This may have some side effects and require to re-initialize some replicas.
The alternate solution to an upgrade is a patch, which is one of the services offered by
ForgeRock to their supported customers.
Kind regards,
Ludovic.
Generated at Mon Mar 07 05:57:14 GMT 2016 using JIRA 6.3.9#6339sha1:46fa26140bf81c66e10e6f784903d4bfb1a521ae.
Download

Word - ForgeRock JIRA