website: Multiple warnings about single server deployment

This commit is contained in:
Armon Dadgar 2014-04-11 12:43:06 -07:00
parent 369f6a3dcf
commit e4b50e2420
3 changed files with 6 additions and 3 deletions

View File

@ -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) 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. 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 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 should ever be running in bootstrap mode*. Once `Node B` and `Node C` are started, you should see a
message to the effect of: message to the effect of:

View File

@ -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 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 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.
<table class="table table-bordered table-striped"> <table class="table table-bordered table-striped">
<tr> <tr>

View File

@ -8,8 +8,9 @@ sidebar_current: "gettingstarted-agent"
After Consul is installed, the agent must be run. The agent can either run 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 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 a recommended 3 or 5. A single server deployment is _**highly**_ discouraged
bootstrapping a new datacenter. All other agents run in client mode, which 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, 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 and forwards queries to servers. The agent must be run for every node that
will be part of the cluster. will be part of the cluster.