luxolus
/
open-nomad
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Merge pull request #3853 from hashicorp/docs-datacenter-faq 

Clarify Nomad dc vs Consul dc
This commit is contained in:
Michael Schurter 2018-02-12 11:31:18 -08:00 committed by GitHub
parent 06397ba59d e3d1a76a08
commit 0b5826bc11
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
website/source/docs/faq.html.md
View File

@ -26,3 +26,18 @@ a [gossip protocol](/docs/internals/gossip.html). The consensus protocol is stro
consistent, and is used for all state replication and scheduling. The gossip protocol
is used to manage the addresses of servers for automatic clustering and multi-region
federation. This means all data that is managed by Nomad is strongly consistent.
## Q: Is Nomad's `datacenter` parameter the same as Consul's?
No. For those familiar with Consul, [Consul's notion of a
datacenter][consul_dc] is more equivalent to a [Nomad region][nomad_region].
Nomad supports grouping nodes into multiple datacenters, which should reflect
nodes being colocated, while being managed by a single set of Nomad servers.
Consul on the other hand does not have this two-tier approach to servers and
agents and instead [relies on federation to create larger logical
clusters][consul_fed].
[consul_dc]: https://www.consul.io/docs/agent/options.html#_datacenter
[consul_fed]: https://www.consul.io/docs/guides/datacenters.html
[nomad_region]: /docs/agent/configuration/index.html#datacenter