From e4b50e2420a005acb64ea78fe0b2323f5a512453 Mon Sep 17 00:00:00 2001 From: Armon Dadgar Date: Fri, 11 Apr 2014 12:43:06 -0700 Subject: [PATCH] website: Multiple warnings about single server deployment --- website/source/docs/guides/bootstrapping.html.markdown | 1 + website/source/docs/internals/consensus.html.markdown | 3 ++- website/source/intro/getting-started/agent.html.markdown | 5 +++-- 3 files changed, 6 insertions(+), 3 deletions(-) diff --git a/website/source/docs/guides/bootstrapping.html.markdown b/website/source/docs/guides/bootstrapping.html.markdown index 75a62abf9b..a617125c47 100644 --- a/website/source/docs/guides/bootstrapping.html.markdown +++ b/website/source/docs/guides/bootstrapping.html.markdown @@ -22,6 +22,7 @@ the following will be logged: Once `Node A` is running, we can start the next set of servers. There is a [deployment table](/docs/internals/consensus.html#toc_3) that covers various options, but it is recommended to have 3 or 5 total servers per data center. +A single server deployment is _**highly**_ discouraged as data loss is inevitable in a failure scenario. We start the next servers **without** specifying `-bootstrap`. This is critical, since only one server should ever be running in bootstrap mode*. Once `Node B` and `Node C` are started, you should see a message to the effect of: diff --git a/website/source/docs/internals/consensus.html.markdown b/website/source/docs/internals/consensus.html.markdown index 0b461d5ba3..ebd9d5a13f 100644 --- a/website/source/docs/internals/consensus.html.markdown +++ b/website/source/docs/internals/consensus.html.markdown @@ -136,7 +136,8 @@ transactions and higher availability without sacrificing consistency. Below is a table that shows for the number of servers how large the quorum is, as well as how many node failures can be tolerated. The -recommended deployment is either 3 or 5 servers. +recommended deployment is either 3 or 5 servers. A single server deployment +is _**highly**_ discouraged as data loss is inevitable in a failure scenario. diff --git a/website/source/intro/getting-started/agent.html.markdown b/website/source/intro/getting-started/agent.html.markdown index c32398f405..8f9f796ef2 100644 --- a/website/source/intro/getting-started/agent.html.markdown +++ b/website/source/intro/getting-started/agent.html.markdown @@ -8,8 +8,9 @@ sidebar_current: "gettingstarted-agent" After Consul is installed, the agent must be run. The agent can either run in a server or client mode. Each datacenter must at least one server, and -a recommended 3 or 5. [This guide](/docs/guides/bootstrapping.html) covers -bootstrapping a new datacenter. All other agents run in client mode, which +a recommended 3 or 5. A single server deployment is _**highly**_ discouraged +as data loss is inevitable in a failure scenario. [This guide](/docs/guides/bootstrapping.html) +covers bootstrapping a new datacenter. All other agents run in client mode, which is a very lightweight process that registers services, runs health checks, and forwards queries to servers. The agent must be run for every node that will be part of the cluster.