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.
|3 months ago|
|.github||5 months ago|
|Documentation||3 months ago|
|api||3 months ago|
|auth||3 months ago|
|client||3 months ago|
|clientv3||3 months ago|
|contrib||3 months ago|
|embed||3 months ago|
|etcdctl||3 months ago|
|etcdmain||3 months ago|
|etcdserver||3 months ago|
|hack||9 months ago|
|lease||3 months ago|
|logos||6 years ago|
|mvcc||3 months ago|
|pkg||3 months ago|
|proxy||3 months ago|
|raft||3 months ago|
|scripts||3 months ago|
|security||5 months ago|
|server/mock||3 months ago|
|tests||3 months ago|
|tools||3 months ago|
|wal||3 months ago|
|.gitignore||3 months ago|
|.header||4 years ago|
|.travis.yml||3 months ago|
|.words||3 months ago|
|ADOPTERS.md||1 year ago|
|CHANGELOG-2.3.md||2 years ago|
|CHANGELOG-3.0.md||1 year ago|
|CHANGELOG-3.1.md||1 year ago|
|CHANGELOG-3.2.md||5 months ago|
|CHANGELOG-3.3.md||5 months ago|
|CHANGELOG-3.4.md||4 months ago|
|CHANGELOG-3.5.md||3 months ago|
|CHANGELOG-4.0.md||1 year ago|
|CONTRIBUTING.md||11 months ago|
|DCO||6 years ago|
|Dockerfile-release||8 months ago|
|Dockerfile-release.arm64||8 months ago|
|Dockerfile-release.ppc64le||8 months ago|
|Dockerfile-release.s390x||8 months ago|
|GOVERNANCE.md||1 year ago|
|LICENSE||7 years ago|
|MAINTAINERS||9 months ago|
|Makefile||3 months ago|
|Procfile||1 year ago|
|Procfile.learner||1 year ago|
|Procfile.v2||1 year ago|
|README.md||3 months ago|
|ROADMAP.md||2 years ago|
|bill-of-materials.json||3 months ago|
|bill-of-materials.override.json||1 year ago|
|build||3 months ago|
|build.bat||4 years ago|
|build.ps1||2 years ago|
|build.sh||3 months ago|
|code-of-conduct.md||1 year ago|
|etcd.conf.yml.sample||2 years ago|
|go.mod||3 months ago|
|go.sum||3 months ago|
|main.go||4 months ago|
|main_test.go||4 months ago|
|test||3 months ago|
|test.sh||3 months 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:
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.
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:
The official etcd ports are 2379 for client requests, and 2380 for peer communication.
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.
See CONTRIBUTING for details on submitting patches and the contribution workflow.
See reporting bugs for details about reporting any issues.
See security disclosure and release process for details on how to report a security vulnerability and how the etcd team manages it.
See issue triage guidelines for details on how issues are managed.
See PR management for guidelines on how pull requests are managed.
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.
etcd is under the Apache 2.0 license. See the LICENSE file for details.