Disabling replication and removing a server from the topology - PingDirectory - 9.3

PingDirectory 9.3

PingDirectory 9.3
PingDirectory 9.3
More than 50% of the servers not being removed from the topology must be online during the process.

When removing a server from the topology, the remaining servers need to be made aware of the change. If additional servers are offline and cannot be online while removing the server, you must distinguish between offline servers that are offline permanently and those that are offline temporarily.

Removing a live server

  • To remove a server that is online, run the dsreplication disable command from any server.
    $ bin/dsreplication disable --hostname austin03.example.com --port 1389 \
    --baseDN dc=example,dc=com --adminUID admin --adminPassword password \

    If the server to remove is online, only one invocation of dsreplication disable is necessary.

Removing an offline server from the topology

  • To remove a defunct or misbehaving server from the topology while that server is offline, run remove-defunct-server from a live server in the topology. Doing this will remove configuration references to the offline server from the topology’s perspective. This is useful if the server is broken and cannot start. For example:
    $ bin/remove-defunct-server --serverInstanceName austin01 \
    --bindDN "cn=Directory Manager" --bindPassword password

    After you have removed the server, you can delete it. However, if you want to keep the server as a standalone server, proceed to Cleaning up an offline defunct server.


    The --ignore-online option removes an online server cleanly from the topology.


    To speed up the process of removing multiple servers, change the default 10-minute timeout for each server you are taking out of rotation by setting the Java virtual machine (JVM) property com.unboundid.connectionutils.LdapResponseTimeoutMillis before you run remove-defunct-server.

Cleaning up an offline defunct server

If you have removed a defunct server and want to keep it as a standalone server, then you also need to run the remove-defunct-server --performLocalCleanup command on the defunct server while it is offline. This will remove configuration references on the offline server, and make it a standalone server. This is useful if a server is temporarily misbehaving, but you want to add it back to the topology at a later time. The remove-defunct-server command will only accept the --performLocalCleanup argument if the server is offline.
  • Run the remove-defunct-server command on each server that is removed from the topology. For example:
    $ bin/remove-defunct-server --performLocalCleanup --no-prompt

    To remove the defunct server, you must include the --no-prompt parameter. If you exclude this parameter, the server won't be removed from the topology. Additionally, the server might attempt to contact additional hosts in the topology, which could result in an error. These are known issues that only apply to --performLocalCleanup and will be corrected in a future release.