status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Minor clarification of server nodes 

In **Node Removal** section, clarify that server nodes are being discussed.
This commit is contained in:
Geoffrey Grosenbach 2018-05-23 14:59:31 -07:00 committed by GitHub
parent cceb79cbc5
commit 071576c0db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/guides/deployment.html.md
View File

@ -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. 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 $ consul operator raft remove-peer -address=x.x.x.x:8300