Go to file
Benjamin Wang 4443e14dcd
Merge pull request #14127 from ahrtr/threshold_3.5
[3.5] Restrict the max size of each WAL entry to the remaining size of the WAL file
2022-06-17 15:03:35 +08:00
.github Make DRY_RUN explicit 2022-05-16 13:10:05 +02:00
api version: bump up to 3.5.4 2022-04-24 12:44:36 +02:00
client Add FileReader and FileBufReader utilities 2022-06-17 09:00:43 +08:00
contrib ClientV3 tests use integration.NewClient that configures proper logger. 2021-04-29 18:18:34 +02:00
Documentation *: regen proto 2021-03-11 11:27:52 -05:00
etcdctl Update golang.org/x/crypto to latest 2022-04-28 09:27:02 -07:00
etcdutl Update golang.org/x/crypto to latest 2022-04-28 09:27:02 -07:00
hack hack,scripts: rename "master" branch references to "main" 2021-05-12 10:40:28 -07:00
logos logos: add SVG and PNG logos 2014-12-18 14:59:06 -08:00
pkg version: bump up to 3.5.4 2022-04-24 12:44:36 +02:00
raft version: bump up to 3.5.4 2022-04-24 12:44:36 +02:00
scripts scripts: Detect staged files before building release 2022-05-18 13:11:10 +02:00
security markdowns: rename "master" branch references to "main" 2021-05-12 10:41:02 -07:00
server restrict the max size of each WAL entry to the remaining size of the file 2022-06-17 09:01:29 +08:00
tests Update golang.org/x/crypto to latest 2022-04-28 09:27:02 -07:00
tools Represent bucket as object instead of []byte name. 2021-05-25 09:22:25 +02:00
.gitignore script/genproto.sh: Refactor to be explicit about versions. 2020-10-08 19:52:27 +02:00
.header .header: update to 'etcd Authors' 2016-05-12 20:56:50 -07:00
.travis.yml Update to go 1.16.15 2022-03-22 00:00:22 +01:00
.words clientv3: Expose clientv3/examples close to the code. 2020-10-08 14:27:32 +02:00
bill-of-materials.json Split etcdctl into etcdctl (public API access) & etcdutl (direct surgery on files) 2021-05-17 11:54:03 +02:00
bill-of-materials.override.json etcd: Replace ghodss/yaml with sigs.k8s.io/yaml 2019-05-02 12:34:36 +05:30
build Fix shellcheck warnings: Escaping. 2021-01-29 22:32:43 +00:00
build.bat vendor: only vendor on emitted binaries 2016-04-05 21:01:16 -07:00
build.ps1 build.ps1: update import paths to "go.etcd.io/etcd" 2018-08-28 17:47:55 -07:00
build.sh Split etcdctl into etcdctl (public API access) & etcdutl (direct surgery on files) 2021-05-17 11:54:03 +02:00
code-of-conduct.md *: update project code of conduct 2019-09-18 14:09:18 -04:00
codecov.yml Split intengration/clientv3 tests into multiple packages 2021-01-23 11:12:44 +01:00
CONTRIBUTING.md markdowns: rename "master" branch references to "main" 2021-05-12 10:41:02 -07:00
DCO docs(readme/contrib): clean up README, merge changes from CONTRIBUTING.md and split out DCO 2014-04-04 10:58:34 -07:00
Dockerfile-release.amd64 Dockerfile-release.*: Update base image snapshot 2022-04-12 10:39:55 +02:00
Dockerfile-release.arm64 Dockerfile-release.*: Update base image snapshot 2022-04-12 10:39:55 +02:00
Dockerfile-release.ppc64le Dockerfile-release.*: Update base image snapshot 2022-04-12 10:39:55 +02:00
Dockerfile-release.s390x Dockerfile-release.*: Update base image snapshot 2022-04-12 10:39:55 +02:00
dummy.go Split etcdctl into etcdctl (public API access) & etcdutl (direct surgery on files) 2021-05-17 11:54:03 +02:00
etcd.conf.yml.sample fix self-signed-cert-validity parameter cannot be specified in the config file 2021-07-30 07:53:43 +08:00
go.mod version: bump up to 3.5.4 2022-04-24 12:44:36 +02:00
go.sum Update golang.org/x/crypto to latest 2022-04-28 09:27:02 -07:00
GOVERNANCE.md *: create project governance 2019-09-30 15:24:14 -04:00
LICENSE License project under the Apache License Version 2.0 2013-07-31 17:39:03 +00:00
MAINTAINERS MAINTAINERS: add wenjiaswe@ and ptabor@ 2021-01-14 15:16:38 -08:00
Makefile Makefile: Fix wrong target 2022-03-31 10:01:15 +02:00
Procfile Procfiles: Added Comments To Procfiles 2019-11-06 08:44:04 +05:30
Procfile.learner Procfiles: Added Comments To Procfiles 2019-11-06 08:44:04 +05:30
Procfile.v2 Procfiles: Added Comments To Procfiles 2019-11-06 08:44:04 +05:30
README.md Rename master to main in README and other *.md files (#12977) 2021-05-15 23:46:05 -07:00
ROADMAP.md *: change roadmap, future release dates 2018-10-01 01:04:24 -07:00
test Fix shellcheck warnings: Escaping. 2021-01-29 22:32:43 +00:00
test.sh server: Add verification of whether lock was called within out outside of apply 2022-04-06 11:22:51 +02:00

etcd

Go Report Card Coverage Tests asset-transparency codeql-analysis self-hosted-linux-arm64-graviton2-tests Docs Godoc Releases LICENSE

Note: The main branch may be in an unstable or even broken state during development. For stable versions, see releases.

etcd Logo

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 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.

Time:

Join Hangouts Meet: meet.google.com/umg-nrxn-qvs

Join by phone: +1 405-792-0633 PIN: 299 906#

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 main branch. This first needs Go installed (version 1.16+ is required). All development occurs on main, including new features and bug fixes. Bug fixes are first targeted at main 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 main 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 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:

goreman start

This will bring up 3 etcd members infra1, infra2 and 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

Next steps

Now it's time to dig into the full etcd API and other guides.

Contact

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

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

License

etcd is under the Apache 2.0 license. See the LICENSE file for details.