OPENDJ 2.7 got M. C. 2147483508 on one of the replica

[joeyabuki]

I am testing on the opendj replication.
My version is 2.7 – 20150120
I got Missing Changes with “2147483508” on one of the replica. I can find any hints in the log. Anyone know what does it mean? And how to fix it?

[Ludo]

Hi,

Can you provide the complete error message from the log ?
Just the 3 words “Missing Changes with …” is not enough to understand the issue.
Could you also describe the steps that you did to test OpenDJ replication, that led to this message ?

[joeyabuki]

I create server A with about 110k records.
Then I create server B,C,D.

I use the following command to initialize server B,C,D
dsreplication initialize –baseDN “o=abc,c=us” –adminUID Admin –adminPassword Password –hostSource serverA.abc.us –portSource 4444 –hostDestination serverB.abc.us –portDestination 4444 -X -n

and I got the replication status like this:
Suffix DN : Server : Entries : Replication enabled : DS ID : RS ID : RS Port (1) : M.C. (2) : A.O.M.C. (3) : Security (4)
———–:———————:———:———————:——-:——-:————-:————:————–:————-
o=abc,c=us : serverA.abc.us:4444 : 115213 : true : 5859 : 15702 : 8989 : 0 : : true
o=abc,c=us : serverB.abc.us:4444 : 115213 : true : 10903 : 3393 : 8989 : 2147483160 : : true
o=abc,c=us : serverC.abc.us:4444 : 115213 : true : 24059 : 3433 : 8989 : 2147483018 : : true
o=abc,c=us : serverD.abc.us:4444 : 115213 : true : 6513 : 2334 : 8989 : 2147483018 : : true

The missing changes is there once i have done the replication initialization. So I don’t understand what the problem is.

[joeyabuki]

error log from serverB

[21/Jan/2015:17:20:52 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381717 msg=Installation Directory: /opt/opendj
[21/Jan/2015:17:20:52 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381719 msg=Instance Directory: /opt/opendj
[21/Jan/2015:17:20:52 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381713 msg=JVM Information: 1.8.0_25-b17 by Oracle Corporation, 64-bit architecture, 893386752 bytes heap size
[21/Jan/2015:17:20:52 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381714 msg=JVM Host: localhost, running Linux 2.6.32-504.3.3.el6.x86_64 amd64, 4016824320 bytes physical memory size, number of processors available 2
[21/Jan/2015:17:20:52 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381715 msg=JVM Arguments: “-Dorg.opends.server.scriptName=start-ds”
[21/Jan/2015:17:20:55 +0700] category=JEB severity=NOTICE msgID=8847402 msg=The database backend Data containing 115213 entries has started
[21/Jan/2015:17:20:55 +0700] category=EXTENSIONS severity=NOTICE msgID=1507549 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: serverB.abc.us
[21/Jan/2015:17:20:56 +0700] category=SYNC severity=NOTICE msgID=15139020 msg=Replication server RS(3393) started listening for new connections on address 0.0.0.0 port 8989
[21/Jan/2015:17:20:56 +0700] category=SYNC severity=NOTICE msgID=15138878 msg=Directory server DS(17163) has connected to replication server RS(3393) for domain “cn=admin data” at serverB.abc.us/127.0.0.1:8989 with generation ID 163944
[21/Jan/2015:17:20:57 +0700] category=SYNC severity=NOTICE msgID=15138878 msg=Directory server DS(10903) has connected to replication server RS(3393) for domain “o=abc,c=us” at serverB.abc.us/127.0.0.1:8989 with generation ID 19115481
[21/Jan/2015:17:20:57 +0700] category=SYNC severity=NOTICE msgID=15138878 msg=Directory server DS(7213) has connected to replication server RS(3393) for domain “cn=schema” at serverB.abc.us/127.0.0.1:8989 with generation ID 8408
[21/Jan/2015:17:20:57 +0700] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on Administration Connector 0.0.0.0 port 4444
[21/Jan/2015:17:20:57 +0700] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAPS Connection Handler 0.0.0.0 port 636
[21/Jan/2015:17:20:57 +0700] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAP Connection Handler 0.0.0.0 port 389
[21/Jan/2015:17:20:57 +0700] category=CORE severity=NOTICE msgID=458887 msg=The Directory Server has started successfully
[21/Jan/2015:17:20:57 +0700] category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887): The Directory Server has started successfully

• This reply was modified 7 years, 6 months ago by joeyabuki.

[joeyabuki]

error log from serverA

[21/Jan/2015:17:20:48 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381717 msg=Installation Directory: /opt/opendj
[21/Jan/2015:17:20:48 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381719 msg=Instance Directory: /opt/opendj
[21/Jan/2015:17:20:48 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381713 msg=JVM Information: 1.8.0_25-b17 by Oracle Corporation, 64-bit architecture, 893386752 bytes heap size
[21/Jan/2015:17:20:48 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381714 msg=JVM Host: localhost, running Linux 2.6.32-504.1.3.el6.x86_64 amd64, 4016816128 bytes physical memory size, number of processors available 2
[21/Jan/2015:17:20:48 +0700] category=RUNTIME_INFORMATION severity=NOTICE msgID=20381715 msg=JVM Arguments: “-Dorg.opends.server.scriptName=start-ds”
[21/Jan/2015:17:20:50 +0700] category=JEB severity=NOTICE msgID=8847402 msg=The database backend Data containing 115213 entries has started
[21/Jan/2015:17:20:50 +0700] category=EXTENSIONS severity=NOTICE msgID=1507549 msg=DIGEST-MD5 SASL mechanism using a server fully qualified domain name of: serverA.abc.us
[21/Jan/2015:17:20:51 +0700] category=SYNC severity=NOTICE msgID=15139020 msg=Replication server RS(3433) started listening for new connections on address 0.0.0.0 port 8989
[21/Jan/2015:17:20:51 +0700] category=SYNC severity=NOTICE msgID=15138878 msg=Directory server DS(13938) has connected to replication server RS(3433) for domain “cn=admin data” at serverA.abc.us/127.0.0.1:8989 with generation ID 163944
[21/Jan/2015:17:20:52 +0700] category=SYNC severity=NOTICE msgID=15138878 msg=Directory server DS(24059) has connected to replication server RS(3433) for domain “o=abc,c=us” at serverA.abc.us/127.0.0.1:8989 with generation ID 19115481
[21/Jan/2015:17:20:52 +0700] category=SYNC severity=NOTICE msgID=15138878 msg=Directory server DS(17811) has connected to replication server RS(3433) for domain “cn=schema” at serverA.abc.us/127.0.0.1:8989 with generation ID 8408
[21/Jan/2015:17:20:52 +0700] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on Administration Connector 0.0.0.0 port 4444
[21/Jan/2015:17:20:52 +0700] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAPS Connection Handler 0.0.0.0 port 636
[21/Jan/2015:17:20:52 +0700] category=PROTOCOL severity=NOTICE msgID=2556180 msg=Started listening for new connections on LDAP Connection Handler 0.0.0.0 port 389
[21/Jan/2015:17:20:52 +0700] category=CORE severity=NOTICE msgID=458887 msg=The Directory Server has started successfully
[21/Jan/2015:17:20:52 +0700] category=CORE severity=NOTICE msgID=458891 msg=The Directory Server has sent an alert notification generated by class org.opends.server.core.DirectoryServer (alert type org.opends.server.DirectoryServerStarted, alert ID 458887): The Directory Server has started successfully

[joeyabuki]

let me know if you want more. thanks!

• This reply was modified 7 years, 6 months ago by joeyabuki.

[Ludo]

It looks like to me that the servers are properly initialized and in sync, but the tool reports an invalid value for the missing changes. We will look into the issue shortly.

[joeyabuki]

ok thanks

[Author]

Posts