From cb5524e1e94d20a7b156ee58463833926bb5071c Mon Sep 17 00:00:00 2001
From: kaitlincarter-hc <43049322+kaitlincarter-hc@users.noreply.github.com>
Date: Mon, 17 Dec 2018 09:16:07 -0600
Subject: [PATCH] Guide Update: Adding/Removing Server  (#5095)

* first draft of updated content for consul leave

* Changed the consul leave/bootstrap_expect scenario into a note
---
 website/source/docs/guides/servers.html.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/source/docs/guides/servers.html.md b/website/source/docs/guides/servers.html.md
index f2015d0d51..742785b1de 100644
--- a/website/source/docs/guides/servers.html.md
+++ b/website/source/docs/guides/servers.html.md
@@ -157,6 +157,8 @@ The leader should also emit various logs including:
 At this point the node has been gracefully removed from the cluster, and
 will shut down.
 
+~> Running `consul leave` on a server explicitly will reduce the quorum size. Even if the cluster used `bootstrap_expect` to set a quorum size initially, issuing `consul leave` on a server will reconfigure the cluster to have fewer servers. This means you could end up with just one server that is still able to commit writes because quorum is only 1, but those writes might be lost if that server fails before more are added.
+
 To remove all agents that accidentally joined the wrong set of servers, clear out the contents of the data directory (`-data-dir`) on both client and server nodes.
 
 These graceful methods to remove servres assumse you have a healthly cluster.