Yicheng Qin 176222a2f4 *: bump to v2.0.13+git | 9 years ago | |
---|---|---|
Documentation | 9 years ago | |
Godeps | 10 years ago | |
client | 9 years ago | |
discovery | 9 years ago | |
error | 10 years ago | |
etcdctl | 9 years ago | |
etcdmain | 9 years ago | |
etcdserver | 9 years ago | |
hack | 10 years ago | |
integration | 9 years ago | |
logos | 10 years ago | |
migrate | 9 years ago | |
pkg | 9 years ago | |
proxy | 9 years ago | |
raft | 9 years ago | |
rafthttp | 9 years ago | |
scripts | 10 years ago | |
snap | 9 years ago | |
store | 9 years ago | |
tools | 9 years ago | |
version | 9 years ago | |
wal | 9 years ago | |
.dockerignore | 10 years ago | |
.gitignore | 10 years ago | |
.godir | 10 years ago | |
.header | 10 years ago | |
.travis.yml | 9 years ago | |
CONTRIBUTING.md | 10 years ago | |
DCO | 10 years ago | |
Dockerfile | 10 years ago | |
LICENSE | 11 years ago | |
MAINTAINERS | 10 years ago | |
NOTICE | 11 years ago | |
Procfile | 10 years ago | |
README.md | 10 years ago | |
build | 9 years ago | |
cover | 10 years ago | |
main.go | 9 years ago | |
test | 9 years ago |
etcd is a distributed, consistent key value store for shared configuration and service discovery with a focus on being:
etcd is written in Go and uses the Raft consensus algorithm to manage a highly-available replicated log.
See etcdctl for a simple command line client. Or feel free to just use curl, as in the examples below.
If you're considering etcd for production use, please see: production-ready.md
The latest release and setup instructions are available at GitHub.
First start a single-member cluster of etcd:
./bin/etcd
This will bring up etcd listening on port 4001 for client communication and on port 7001 for server-to-server communication.
Next, let's set a single key, and then retrieve it:
curl -L http://127.0.0.1:4001/v2/keys/mykey -XPUT -d value="this is awesome"
curl -L http://127.0.0.1:4001/v2/keys/mykey
You have successfully started an etcd and written a key to the store.
First install goreman, which manages Procfile-based applications.
Our Profile script will set up a local example cluster. You can start it with:
goreman start
This will bring up 3 etcd members infra1
, infra2
and infra3
and etcd proxy proxy
, which runs locally and composes a cluster.
You can write a key to the cluster and retrieve the value back from any member or proxy.
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.
etcd uses semantic versioning New minor versions may add additional features to the API.
You can get the version of etcd by issuing a request to /version:
curl -L http://127.0.0.1:4001/version
The v2
API responses should not change after the 2.0.0 release but new features will be added over time.
etcd has known issues on 32-bit systems due to a bug in the Go runtime. See #358 for more information.
etcd is under the Apache 2.0 license. See the LICENSE file for details.