PingDirectory

Disabling replication and removing a server from the topology

When removing a server from a replication topology, you must make the remaining servers in the topology aware of the change by running the appropriate command.

Before you begin

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

If some of the remaining servers in the topology are offline temporarily, they update automatically after they come online. However, if some of the remaining servers are offline permanently, you must remove them using the remove-defunct-server command after you have removed the desired server.

Removing a server from the topology

Steps

  • To remove a server from the topology:

    Choose from:

    • If the server’s online, and you need to remove it, run the dsreplication disable command from any server in the topology. For example:

      $ bin/dsreplication disable --hostname austin03.example.com --port 1389 \
        --baseDN dc=example,dc=com --adminUID admin --adminPassword password \
        --no-prompt
    • If you need to permanently remove a server that’s offline because it’s defunct or malfunctioning, run remove-defunct-server from a live server in the topology. For example:

      $ bin/remove-defunct-server --serverInstanceName austin01 \
        --bindDN "cn=Directory Manager" --bindPassword password
      • To speed up removing multiple servers, change the default 10-minute timeout for each server you’re taking out of rotation by setting the Java Virtual Machine (JVM) property com.unboundid.connectionutils.LdapResponseTimeoutMillis before you run remove-defunct-server.

      • The --ignore-online option removes an online server cleanly from the topology when you can’t remove it using dsreplication disable.

      Result:

      The remove-defunct-server command removed configuration references to the offline server from the topology’s perspective.

      After you have removed the server, you can delete it. However, if you want to keep the server as a standalone server, refer to Turn a defunct server into a standalone server.

Turn a defunct server into a standalone server

If you’ve removed a defunct server and want to keep it as a standalone server, run the remove-defunct-server --performLocalCleanup command on the defunct server while it’s offline. This command removes all topology configuration references on the offline server and makes it a standalone server.

You can use this option if you want to add the server back to the topology at a later time.