github.com/technosophos/deis@v1.7.1-0.20150915173815-f9005256004b/docs/_includes/_isolating-etcd-description.rst (about) 1 The Deis Control Plane, Data Plane, and Router Mesh components all depend on an 2 etcd cluster for service discovery and configuration. 3 4 Whether built for evaluation or to host production applications, when managing a 5 small Deis cluster (three to five nodes), it is reasonable to accept the 6 platform's default behavior wherein etcd runs on every node within the cluster. 7 8 In larger Deis clusters however, running etcd on every node can have a 9 deleterious effect on overall cluster performance since it increases the time 10 required for nodes to reach consensus on writes and leader elections. In such 11 cases, it is beneficial to isolate etcd to a small, fixed number of nodes. All 12 other nodes in the Deis cluster may run an etcd proxy. Proxies will forward 13 read and write requests to active participants in the etcd cluster (leader or 14 followers) without affecting the time required for etcd nodes to reach consensus 15 on writes or leader elections. 16 17 .. note:: 18 19 The benefit of running an etcd proxy on any node not running a full etcd 20 process is that any container or service depending on etcd can connect to 21 etcd easily via ``localhost`` from any node in the Deis cluster. 22 23 Also see `CoreOS cluster architecture documentation`_ for further details. 24 25 .. _`CoreOS cluster architecture documentation`: https://coreos.com/os/docs/latest/cluster-architectures.html#production-cluster-with-central-services