From 071576c0db3adf6763e06f620cd4b0e445e1e115 Mon Sep 17 00:00:00 2001 From: Geoffrey Grosenbach Date: Wed, 23 May 2018 14:59:31 -0700 Subject: [PATCH] Minor clarification of server nodes In **Node Removal** section, clarify that server nodes are being discussed. --- website/source/docs/guides/deployment.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/guides/deployment.html.md b/website/source/docs/guides/deployment.html.md index 28c473ed7e..97341404d7 100644 --- a/website/source/docs/guides/deployment.html.md +++ b/website/source/docs/guides/deployment.html.md @@ -167,7 +167,7 @@ Failed nodes will be automatically removed after 72 hours. This can happen if a This sequence can be accelerated with the [`force-leave`](https://www.consul.io/docs/commands/force-leave.html) command. Nodes running as servers will be removed from the Raft quorum. Force-leave may also be used to remove nodes that have accidentally joined the datacenter. Force-leave can only be applied to the nodes in its respective datacenter and cannot be executed on the nodes outside the datacenter. -Alternately, nodes can also be removed using `remove-peer` if `force-leave` is not effective in removing the nodes. +Alternately, server nodes can also be removed using `remove-peer` if `force-leave` is not effective in removing the nodes. $ consul operator raft remove-peer -address=x.x.x.x:8300