From ac288bad21c8f4e874c7c55dc95966e8efc116e6 Mon Sep 17 00:00:00 2001
From: danielehc <40759828+danielehc@users.noreply.github.com>
Date: Fri, 25 Jan 2019 21:20:48 +0100
Subject: [PATCH] Adding quorum note on leave command page (#5102)

Reusing the same phrasing as  https://github.com/hashicorp/consul/pull/5095/ to provide info on the effects of the `consul leave` command on Consul quorum
---
 website/source/docs/commands/leave.html.markdown.erb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/website/source/docs/commands/leave.html.markdown.erb b/website/source/docs/commands/leave.html.markdown.erb
index 1b436ff1b..b99d7296b 100644
--- a/website/source/docs/commands/leave.html.markdown.erb
+++ b/website/source/docs/commands/leave.html.markdown.erb
@@ -19,6 +19,9 @@ For nodes in server mode, the node is removed from the Raft peer set
 in a graceful manner. This is critical, as in certain situations a
 non-graceful leave can affect cluster availability.
 
+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.
+
 ## Usage
 
 Usage: `consul leave [options]`