Uninstall

Remove a V7 server on Windows or Linux, take a node out of a cluster, tear down an X8 Compose stack, keep the configuration directory and the license you may need again, and know what dock shows afterwards.

What you will do: take a server, a node or a whole deployment out of service without losing what you may need later.

Before you remove anything

  • Keep the external configuration directory. A fresh installation pointed at it inherits the whole configuration (that is also how a replacement node joins a cluster). Copy it, or leave it in place; the uninstaller only removes the installation directory. See Backup and restore.
  • Copy the hot data and the archive you still need, with the services stopped.
  • Plan the license. A license is dedicated to one server or cluster and is issued against its server key (PortX > Settings > License); if the new installation shows a different key, request a new license file. See How licensing works.
  • Take a node out of a cluster first. V7: stop the node, remove its name from cluster.allowedMasters if it was a processor, and move the listener accounts that named it as listening or indexing node. X8: delete its <alias>-<role>.node file from conf/registry/ (Traefik drops it from the pool within ten seconds), then stop its compose project. Removing a member from IGNITE_CMG_NODES and IGNITE_META_STORAGE_NODES (the fixed odd-numbered quorum) is not documented — pending engineering; plan the quorum so that a server you may retire is not in it.

V7 on Windows

  1. Run Uninstall XpoLog.exe from <install dir>\UninstallerData (or remove XPLG from the Windows control panel) and follow the wizard. Nothing of the installation remains on the machine.
  2. If you created extra services for a multi-process cluster, remove them: sc delete <service name>.
  3. The external configuration directory and data on other volumes are not touched — keep or delete them yourself.

V7 on Linux

  1. Run Uninstall XpoLog.bin from <install dir>/UninstallerData (a command-line wizard), or simply delete the installation directory.
  2. Remove the service you created — the unit at /etc/systemd/system/XPLG.service (systemctl disable --now XPLG) or the init.d script — and the limits.conf entries for the XPLG user if nothing else needs them.
  3. Keep or delete the external configuration directory and the data directories.

The wiki also describes removing a WAR deployment from an application server; that packaging is no longer shipped.

X8 Compose

C="docker compose -f docker-compose.yml -f docker-compose.traefik.yml"
$C down --remove-orphans                                 # stop; bind-mounted data stays
sudo rm -rf "$XPLG_BASE_HOST_PATH" "$XPLG_SHARED_HOST_PATH"   # only when the data is no longer needed
sudo ./xplg-open-ports.sh ./.env --remove                # the same options you opened with
docker image rm <XPLG_IMAGE>

To rebuild on the same host instead of removing it, follow the full reset on Docker (--fix-dirs, then up -d). The NFS export and the cloud firewall rules are yours to remove.

In dock

There is no retire action in dock yet. The deployment keeps its last reported values and reads as stale seven days after its last heartbeat. A reinstalled server that sends a first heartbeat with the license key appears as a new row with a new token; see Register a deployment. Uninstalling does not end a license term; renewals and cancellation are on Renewals and multi-year terms.

Next: PortX

Source: XPLG wiki, pages 1597014255, 1594133322, 1602191784, 1602191782, 3151659011, 3150544899, 3150807046, 1594132180, 1594133274, 1594132401 (https://xpolog.atlassian.net/wiki/spaces/XPOL/pages/1597014255); dock deployments module. Pending from XPLG engineering: removing a member from the X8 Ignite quorum.