![]() This fixes failed RPC rate query, where we do not need subtraction because we already query by the status code. Also adds grpc_method to make it more specific. Most of the time, the failure recovers within 10-second, which is our Prometheus scrap interval, so 'rate' query might not cover that time window, showing as 0s, but still shows up in the graph. Signed-off-by: Gyu-Ho Lee <gyuhox@gmail.com> |
||
---|---|---|
.. | ||
benchmarks | ||
dev-guide | ||
dev-internal | ||
learning | ||
op-guide | ||
platforms | ||
rfc | ||
upgrades | ||
v2 | ||
README.md | ||
branch_management.md | ||
demo.md | ||
dl_build.md | ||
docs.md | ||
faq.md | ||
integrations.md | ||
metrics.md | ||
production-users.md | ||
reporting_bugs.md | ||
tuning.md |
README.md
Documentation
etcd is a distributed key-value store designed to reliably and quickly preserve and provide access to critical data. It enables reliable distributed coordination through distributed locking, leader elections, and write barriers. An etcd cluster is intended for high availability and permanent data storage and retrieval.
Getting started
New etcd users and developers should get started by downloading and building etcd. After getting etcd, follow this quick demo to see the basics of creating and working with an etcd cluster.
Developing with etcd
The easiest way to get started using etcd as a distributed key-value store is to set up a local cluster.
- Setting up local clusters
- Interacting with etcd
- gRPC etcd core and etcd concurrency API references
- HTTP JSON API through the gRPC gateway
- gRPC naming and discovery
- Client and proxy namespacing
- Embedding etcd
- Experimental features and APIs
- System limits
Operating etcd clusters
Administrators who need to create reliable and scalable key-value stores for the developers they support should begin with a cluster on multiple machines.
- Setting up etcd clusters
- Setting up etcd gateways
- Setting up etcd gRPC proxy
- Hardware recommendations
- Configuration
- Security
- Authentication
- Monitoring
- Maintenance
- Understand failures
- Disaster recovery
- Performance
- Versioning
Platform guides
- Supported systems
- Docker container
- Container Linux, systemd
- rkt container
- Amazon Web Services
- FreeBSD
Upgrading and compatibility
- Migrate applications from using API v2 to API v3
- Upgrading a v2.3 cluster to v3.0
- Upgrading a v3.0 cluster to v3.1
- Upgrading a v3.1 cluster to v3.2
Learning
To learn more about the concepts and internals behind etcd, read the following pages:
Frequently Asked Questions (FAQ)
Answers to common questions about etcd.