c5a9d54835
Keep more wal entries in memory for fast follower recovery. 10,000 was a too small number that triggers quite a few snapshots. ZK proves that 100,000 is a reasonable number for even old less prowerful machines. Eventually we should provide both count and max memory (for large entries).
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
- API references
- gRPC gateway
- gRPC naming and discovery
- 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 (pre-alpha)
- Run etcd clusters inside containers
- Hardware recommendations
- Configuration
- Security
- Monitoring
- Maintenance
- Understand failures
- Disaster recovery
- Performance
- Versioning
- Supported platform
Learning
To learn more about the concepts and internals behind etcd, read the following pages:
- Why etcd (TODO)
- Understand data model
- Understand APIs
- Glossary
- Internals (TODO)
Upgrading and compatibility
Frequently Asked Questions (FAQ)
Answers to common questions about etcd.