053810b0b6
mirror_maker doc mentioned "Data under the destination cluster’s mirroring prefix should be treated as read only." To avoid confusion, read only is being removed and a clear statement mentions that the updated values at destination wont be replicated from destination to origin. wont -> won't |
||
|---|---|---|
| .github | ||
| Documentation | ||
| auth | ||
| client | ||
| clientv3 | ||
| contrib | ||
| docs | ||
| embed | ||
| etcdctl | ||
| etcdmain | ||
| etcdserver | ||
| functional | ||
| hack | ||
| integration | ||
| lease | ||
| logos | ||
| mvcc | ||
| pkg | ||
| proxy | ||
| raft | ||
| scripts | ||
| tests | ||
| tools | ||
| vendor | ||
| version | ||
| wal | ||
| .gitignore | ||
| .header | ||
| .travis.yml | ||
| .words | ||
| CHANGELOG-2.3.md | ||
| CHANGELOG-3.0.md | ||
| CHANGELOG-3.1.md | ||
| CHANGELOG-3.2.md | ||
| CHANGELOG-3.3.md | ||
| CHANGELOG-3.4.md | ||
| CHANGELOG-3.5.md | ||
| CHANGELOG-4.0.md | ||
| CONTRIBUTING.md | ||
| DCO | ||
| Dockerfile-release | ||
| Dockerfile-release.arm64 | ||
| Dockerfile-release.ppc64le | ||
| Gopkg.lock | ||
| Gopkg.toml | ||
| LICENSE | ||
| MAINTAINERS | ||
| MAINTAINERS_RULES.md | ||
| Makefile | ||
| NOTICE | ||
| Procfile | ||
| Procfile.v2 | ||
| README.md | ||
| ROADMAP.md | ||
| bill-of-materials.json | ||
| bill-of-materials.override.json | ||
| build | ||
| build.bat | ||
| build.ps1 | ||
| code-of-conduct.md | ||
| etcd.conf.yml.sample | ||
| functional.yaml | ||
| main.go | ||
| main_test.go | ||
| test | ||
README.md
etcd
Note: The master branch may be in an unstable or even broken state during development. Please use releases instead of the master branch in order to get stable binaries.
the etcd v2 documentation has moved
etcd is a distributed reliable key-value store for the most critical data of a distributed system, with a focus on being:
- Simple: well-defined, user-facing API (gRPC)
- Secure: automatic TLS with optional client cert authentication
- Fast: benchmarked 10,000 writes/sec
- Reliable: properly distributed using Raft
etcd is written in Go and uses the Raft consensus algorithm to manage a highly-available replicated log.
etcd is used in production by many companies, and the development team stands behind it in critical deployment scenarios, where etcd is frequently teamed with applications such as Kubernetes, locksmith, vulcand, Doorman, and many others. Reliability is further ensured by rigorous testing.
See etcdctl for a simple command line client.
Community meetings
etcd contributors and maintainers have bi-weekly meetings at 11:00 AM (USA Pacific) on Tuesdays. Anyone is welcome to join via BlueJeans. An initial agenda will be posted to the shared Google docs a day before each meeting, and everyone is welcome to suggest additional topics or other agendas.
Getting started
Getting etcd
The easiest way to get etcd is to use one of the pre-built release binaries which are available for OSX, Linux, Windows, and Docker on the release page.
For more installation guides, please check out play.etcd.io and operating etcd.
For those wanting to try the very latest version, build the latest version of etcd from the master branch. This first needs Go installed (version 1.10+ is required). All development occurs on master, including new features and bug fixes. Bug fixes are first targeted at master and subsequently ported to release branches, as described in the branch management guide.
Running etcd
First start a single-member cluster of etcd.
If etcd is installed using the pre-built release binaries, run it from the installation location as below:
/tmp/etcd-download-test/etcd
The etcd command can be simply run as such if it is moved to the system path as below:
mv /tmp/etcd-download-test/etcd /usr/local/bin/
etcd
If etcd is built from the master branch, run it as below:
./bin/etcd
This will bring up etcd listening on port 2379 for client communication and on port 2380 for server-to-server communication.
Next, let's set a single key, and then retrieve it:
ETCDCTL_API=3 etcdctl put mykey "this is awesome"
ETCDCTL_API=3 etcdctl get mykey
etcd is now running and serving client requests. For more, please check out:
etcd TCP ports
The official etcd ports are 2379 for client requests, and 2380 for peer communication.
Running a local etcd cluster
First install goreman, which manages Procfile-based applications.
Our Procfile script will set up a local example cluster. Start it with:
goreman start
This will bring up 3 etcd members infra1, infra2 and infra3 and etcd grpc-proxy, which runs locally and composes a cluster.
Every cluster member and proxy accepts key value reads and key value writes.
Running etcd on Kubernetes
To run an etcd cluster on Kubernetes, try etcd operator.
Next steps
Now it's time to dig into the full etcd API and other guides.
- Read the full documentation.
- Explore the full gRPC API.
- Set up a multi-machine cluster.
- Learn the config format, env variables and flags.
- Find language bindings and tools.
- Use TLS to secure an etcd cluster.
- Tune etcd.
Contact
- Mailing list: etcd-dev
- IRC: #etcd on freenode.org
- Planning/Roadmap: milestones, roadmap
- Bugs: issues
Contributing
See CONTRIBUTING for details on submitting patches and the contribution workflow.
Reporting bugs
See reporting bugs for details about reporting any issues.
Reporting a security vulnerability
Due to their public nature, GitHub and mailing lists are NOT appropriate places for reporting vulnerabilities. Please refer to CoreOS's security disclosure process when reporting issues that may be security related.
License
etcd is under the Apache 2.0 license. See the LICENSE file for details.