PingDS

Replication status

The following command displays a snapshot of replication monitoring information:

$ dsrepl \
 status \
 --showChangelogs \
 --showGroups \
 --showReplicas \
 --hostname localhost \
 --port 4444 \
 --bindDN uid=monitor \
 --bindPassword password \
 --trustStorePath /path/to/opendj/config/keystore \
 --trustStorePassword:file /path/to/opendj/config/keystore.pin \
 --no-prompt
Show output

This example shows the output for two replicated servers:

Base DN / RS / DS  Status  Group    Receive     Replay      Entry count  Hostname
                                    delay (ms)  delay (ms)
----------------------------------------------------------------------------------
dc=example,dc=com
├─ RS/Server1      GOOD    default                                       localhost
|  └─ DS/Server1   GOOD    default           0           0       100181  localhost
└─ RS/Server2      GOOD    default                                       localhost
   └─ DS/Server2   GOOD    default           0           0       100181  localhost
uid=Monitor
├─ RS/Server1      GOOD    default                                       localhost
|  └─ DS/Server1   GOOD    default           0           0            1  localhost
└─ RS/Server2      GOOD    default                                       localhost
   └─ DS/Server2   GOOD    default           0           0            1  localhost
cn=schema
├─ RS/Server1      GOOD    default                                       localhost
|  └─ DS/Server1   GOOD    default           0           0            1  localhost
└─ RS/Server2      GOOD    default                                       localhost
   └─ DS/Server2   GOOD    default           0           0            1  localhost

Learn more about the command output in the dsrepl status command reference.

The command connects to each known server to read status information. It will eventually time out if other servers cannot be contacted.

To get a balanced view of replication delays, monitor them over time. You can do this with repeated use of the dsrepl status command, or by reading the monitoring information over LDAP or HTTP. For details, refer to Replication delay (Prometheus) or Replication delay (LDAP).