From f83c7f8a42e9b780b52ca1c17df0db7003c797aa Mon Sep 17 00:00:00 2001 From: Brian Shumate Date: Thu, 23 Mar 2017 13:00:23 -0400 Subject: [PATCH] docs: Point of clarifcation about cluster leadership for #2782 --- website/source/docs/guides/outage.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/guides/outage.html.markdown b/website/source/docs/guides/outage.html.markdown index d82745e9d1..0e16bbe18b 100644 --- a/website/source/docs/guides/outage.html.markdown +++ b/website/source/docs/guides/outage.html.markdown @@ -55,7 +55,7 @@ server if it's still a member of the cluster. If [`consul force-leave`](/docs/commands/force-leave.html) isn't able to remove the server, you have two methods available to remove it, depending on your version of Consul: -* In Consul 0.7 and later, you can use the [`consul operator`](/docs/commands/operator.html#raft-remove-peer) command to remove the stale peer server on the fly with no downtime. +* In Consul 0.7 and later, you can use the [`consul operator`](/docs/commands/operator.html#raft-remove-peer) command to remove the stale peer server on the fly with no downtime if the cluster has a leader. * In versions of Consul prior to 0.7, you can manually remove the stale peer server using the `raft/peers.json` recovery file on all remaining servers. See