How to verify OpenDJ replication topology

This topic has 8 replies, 4 voices, and was last updated 5 years, 5 months ago by Brad Tumy.

  • Author
    Posts
  • #15135
     nkarthik
    Participant

    Is there any command to check the replication topology of an existing distributed environment? I am interested on finding what all opendj’s are connected to a particular replicator and what all replicators are connected to each other etc.

    #15136
     Ludo
    Moderator

    All of this information is available under cn=monitor on any of the Directory Servers.

    #15137
     nkarthik
    Participant

    Is there any specific command to get these details?

    #15138
     Ludo
    Moderator

    ldapsearch -b “cn=monitor” …

    #15139
     Brad Tumy
    Participant

    You might want to check out Chris Ridd’s utilities as well:

    https://github.com/chrisridd/opendj-utils

    topology2dot – displays a replication topology in Graphviz DOT format

    Of course keep in mind that those utilities are not supported.

    Also, you can do an ldapsearch to get the data from cn=monitor or connect with an LDAP client (e.g. Apache Directory Studio).

    #15140
     nkarthik
    Participant

    Thanks. I got the details by searching for connected-to attribute.
    – Is it possible for one opendj cts server to connect to multiple replicators?
    – Also, is it possible to check the entire topology from one server or should I login to each server and check the cn=monitor for connected-to attribute?

    #15149
     JnRouvignac
    Participant

    – Is it possible for one opendj cts server to connect to multiple replicators?

    An OpenDJ directory server is only ever connected to a single OpenDJ replication server at any time. However it may switch if the replication server becomes unavailable.

    – Also, is it possible to check the entire topology from one server or should I login to each server and check the cn=monitor for connected-to attribute?

    I think contacting only one server is enough.
    By querying a server with the commands shown above, what you get back is what this specific server knows about the state of the topology. There is no guarantee this is exactly what the topology is at that moment. However, I think it is good enough and up to date enough.
    Only look at other servers in the case you detect a problem.

    #15170
     nkarthik
    Participant

    As you said, if I search for cn=monitor in a particular cts server, it shows only connectivity information specific to that server. But, we have around 30 cts servers across different sites. I was searching for a took which can show the entire topology at once instead of login to each server and checking.

    #15174
     Brad Tumy
    Participant

    If you run, “./dsreplication status” I believe this will list all servers in the replication agreement.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.

©2022 ForgeRock - we provide an identity and access platform to secure every online relationship for the enterprise market, educational sector and even entire countries. Click to view our privacy policy and terms of use.

Log in with your credentials

Forgot your details?