This fixes etcd being unable to send any message longer than 64 KB as a notification over the websocket. This was because the older version of grpc-websocket-proxy was used and WithMaxRespBodyBufferSize option wasn't set.
|2 years ago|
|.github||2 years ago|
|Documentation||2 years ago|
|api||2 years ago|
|auth||2 years ago|
|client||2 years ago|
|clientv3||2 years ago|
|contrib||2 years ago|
|embed||2 years ago|
|etcdctl||2 years ago|
|etcdmain||2 years ago|
|etcdserver||2 years ago|
|hack||2 years ago|
|lease||2 years ago|
|logos||8 years ago|
|mvcc||2 years ago|
|pkg||2 years ago|
|proxy||2 years ago|
|raft||2 years ago|
|scripts||2 years ago|
|security||2 years ago|
|server/mock||2 years ago|
|tests||2 years ago|
|tools||2 years ago|
|wal||2 years ago|
|.gitignore||2 years ago|
|.header||6 years ago|
|.travis.yml||2 years ago|
|.words||2 years ago|
|ADOPTERS.md||3 years ago|
|CHANGELOG-2.3.md||4 years ago|
|CHANGELOG-3.0.md||3 years ago|
|CHANGELOG-3.1.md||3 years ago|
|CHANGELOG-3.2.md||2 years ago|
|CHANGELOG-3.3.md||2 years ago|
|CHANGELOG-3.4.md||2 years ago|
|CHANGELOG-3.5.md||2 years ago|
|CHANGELOG-4.0.md||2 years ago|
|CONTRIBUTING.md||2 years ago|
|DCO||8 years ago|
|Dockerfile-release||2 years ago|
|Dockerfile-release.arm64||2 years ago|
|Dockerfile-release.ppc64le||2 years ago|
|Dockerfile-release.s390x||2 years ago|
|GOVERNANCE.md||3 years ago|
|LICENSE||9 years ago|
|MAINTAINERS||2 years ago|
|Makefile||2 years ago|
|Procfile||3 years ago|
|Procfile.learner||3 years ago|
|Procfile.v2||3 years ago|
|README.md||2 years ago|
|ROADMAP.md||4 years ago|
|bill-of-materials.json||2 years ago|
|bill-of-materials.override.json||3 years ago|
|build||2 years ago|
|build.bat||6 years ago|
|build.ps1||4 years ago|
|build.sh||2 years ago|
|code-of-conduct.md||3 years ago|
|etcd.conf.yml.sample||4 years ago|
|go.mod||2 years ago|
|go.sum||2 years ago|
|main.go||2 years ago|
|main_test.go||2 years ago|
|test||2 years ago|
|test.sh||2 years ago|
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.
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.
etcd contributors and maintainers have monthly (every four weeks) meetings at 11:00 AM (USA Pacific) on Thursday.
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.
- Jan 10th, 2019 11:00 AM video
- Feb 7th, 2019 11:00 AM video
- Mar 7th, 2019 11:00 AM video
- Apr 4th, 2019 11:00 AM video
- May 2nd, 2019 11:00 AM video
- May 30th, 2019 11:00 AM video
- Jul 11th, 2019 11:00 AM video
- Jul 25, 2019 11:00 AM video
- Aug 22, 2019 11:00 AM video
- Sep 19, 2019 11:00 AM video
- Nov 14, 2019 11:00 AM
- Dec 12, 2019 11:00 AM
- Jan 09, 2020 11:00 AM
- Feb 06, 2020 11:00 AM
- Mar 05, 2020 11:00 AM
- Apr 02, 2020 11:00 AM
- Apr 30, 2020 11:00 AM
- May 28, 2020 11:00 AM
- Jun 25, 2020 11:00 AM
- Jul 23, 2020 11:00 AM
- Aug 20, 2020 11:00 AM
- Sep 17, 2020 11:00 AM
- Oct 15, 2020 11:00 AM
- Nov 12, 2020 11:00 AM
- Dec 10, 2020 11:00 AM
Join Hangouts Meet: meet.google.com/umg-nrxn-qvs
Join by phone: +1 405-792-0633 PIN: 299 906#
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 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.13+ 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.
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:
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:
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 put mykey "this is awesome" 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:
This will bring up 3 etcd members
infra3 and optionally etcd
grpc-proxy, which runs locally and composes a cluster.
Every cluster member and proxy accepts key value reads and key value writes.
Follow the steps in Procfile.learner to add a learner node to the cluster. Start the learner node with:
goreman -f ./Procfile.learner start
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.
- Mailing list: etcd-dev
- IRC: #etcd on freenode.org
- Planning/Roadmap: milestones, roadmap
- Bugs: issues
See CONTRIBUTING for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issues.
Reporting a security vulnerability
See security disclosure and release process for details on how to report a security vulnerability and how the etcd team manages it.
Issue and PR management
See issue triage guidelines for details on how issues are managed.
See PR management for guidelines on how pull requests are managed.
etcd Emeritus Maintainers
These emeritus maintainers dedicated a part of their career to etcd and reviewed code, triaged bugs, and pushed the project forward over a substantial period of time. Their contribution is greatly appreciated.
- Fanmin Shi
- Anthony Romano
etcd is under the Apache 2.0 license. See the LICENSE file for details.