From c27fdb2e72fc37a54e860930b5ccd9599a8b19dc Mon Sep 17 00:00:00 2001 From: Alexandre Pinon Date: Thu, 25 Jan 2018 11:16:21 +0100 Subject: [PATCH] Remove/destroy DTR replica I think the actual documentation can be confusing. In fact if we want to completely remove a DTR cluster, we can use the destroy command, it is fine. But, if we just want to remove a replica from a cluster, it is better to use the remove command which is safer and cleaner. The destroy command do not send a notification to the RethinkDB on the others replicas which can be dangerous and leads to unhealthy DTR clusters. --- .../dtr/2.4/guides/admin/install/uninstall.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/datacenter/dtr/2.4/guides/admin/install/uninstall.md b/datacenter/dtr/2.4/guides/admin/install/uninstall.md index e4228df28b..26d8c28c43 100644 --- a/datacenter/dtr/2.4/guides/admin/install/uninstall.md +++ b/datacenter/dtr/2.4/guides/admin/install/uninstall.md @@ -5,7 +5,13 @@ keywords: dtr, install, uninstall --- Uninstalling DTR can be done by simply removing all data associated with each -replica. To do that, you just run the destroy command once per replica: +replica. To do that, you just run the remove command once per replica and destroy the last one : + +```none +docker run -it --rm \ + docker/dtr:{{ page.dtr_version }} remove \ + --ucp-insecure-tls +``` ```none docker run -it --rm \ @@ -14,10 +20,10 @@ docker run -it --rm \ ``` You will be prompted for the UCP URL, UCP credentials, and which replica to -destroy. +remove/destroy. -To see what options are available in the destroy command, check the -[destroy command reference documentation](../../../reference/cli/destroy.md). +To see what options are available in the remove/destroy commands, check the +[remove command reference documentation](../../../reference/cli/remove.md) and [destroy command reference documentation](../../../reference/cli/destroy.md). ## Where to go next