status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Website: revert changes to 'data center' from 'datacenter'

This commit is contained in:
Ryan Breen 2015-02-19 17:32:31 -05:00
parent f47b70e7bb
commit 92e193161f
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/source/intro/getting-started/agent.html.markdown
View File

@ -3,16 +3,16 @@ layout: "intro"
page_title: "Run the Agent"
sidebar_current: "gettingstarted-agent"
description: |-
After Consul is installed, the agent must be run. The agent can either run in a server or client mode. Each data center must have at least one server, although 3 or 5 is recommended. A single server deployment is highly discouraged as data loss is inevitable in a failure scenario.
After Consul is installed, the agent must be run. The agent can either run in a server or client mode. Each datacenter must have at least one server, although 3 or 5 is recommended. A single server deployment is highly discouraged as data loss is inevitable in a failure scenario.
---
# Run the Consul Agent
After Consul is installed, the agent must be run. The agent can run either
in server or client mode. Each data center must have at least one server,
in server or client mode. Each datacenter must have at least one server,
although 3 or 5 is recommended. 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 data center.
covers bootstrapping a new datacenter.
All other agents run in client mode, a very lightweight
process that registers services, runs health checks, and forwards queries to

8
website/source/intro/index.html.markdown
View File

@ -35,7 +35,7 @@ key features:
store for any number of purposes, including dynamic configuration, feature flagging,
coordination, leader election, and more. The simple HTTP API makes it easy to use.
* **Multi Data Center**: Consul supports multiple data centers out of the box. This
* **Multi Datacenter**: Consul supports multiple datacenters out of the box. This
means users of Consul do not have to worry about building additional layers of
abstraction to grow to multiple regions.
@ -58,15 +58,15 @@ The agents talk to one or more _Consul servers_. The Consul servers are
where data is stored and replicated. The servers themselves elect a leader.
While Consul can function with one server, 3 to 5 is recommended to avoid
failure scenarios leading to data loss. A cluster of Consul servers is recommended
for each data center.
for each datacenter.
Components of your infrastructure that need to discover other services
or nodes can query any of the Consul servers _or_ any of the Consul agents.
The agents forward queries to the servers automatically.
Each data center runs a cluster of Consul servers. When a cross-data center
Each datacenter runs a cluster of Consul servers. When a cross-datacenter
service discovery or configuration request is made, the local Consul servers
forward the request to the remote data center and return the result.
forward the request to the remote datacenter and return the result.
## Next Steps