Version v3.6-DRAFT of the documentation is in DRAFT status. For the latest stable documentation, see v3.5.
This document defines the various terms used in etcd documentation, command line and source code.
The etcd server raises an alarm whenever the cluster needs operator intervention to remain reliable.
Authentication manages user access permissions for etcd resources.
A client connects to the etcd cluster to issue service requests such as fetching key-value pairs, writing data, or watching for updates.
Cluster consists of several members.
The node in each member follows raft consensus protocol to replicate logs. Cluster receives proposals from members, commits them and apply to local store.
Compaction discards all etcd event history and superseded keys prior to a given revision. It is used to reclaim storage space in the etcd backend database.
The etcd cluster holds elections among its members to choose a leader as part of the raft consensus protocol.
A URL pointing to an etcd service or resource.
A user-defined identifier for storing and retrieving user-defined values in etcd.
A set of keys containing either an individual key, a lexical interval for all x such that a < x <= b, or all keys greater than a given key.
The set of all keys in an etcd cluster.
A short-lived renewable contract that deletes keys associated with it on its expiry.
A logical etcd server that participates in serving an etcd cluster.
The first revision to hold the last write to a given key.
Peer is another member of the same cluster.
A proposal is a request (for example a write request, a configuration change request) that needs to go through raft protocol.
The number of active members needed for consensus to modify the cluster state. etcd requires a member majority to reach quorum.
A 64-bit cluster-wide counter that starts at 1 and is incremented each time the keyspace is modified.
A unit of permissions over a set of key ranges which may be granted to a set of users for access control.
A point-in-time backup of the etcd cluster state.
The physical storage backing the cluster keyspace.
An atomically executed set of operations. All modified keys in a transaction share the same modification revision.
The number of writes to a key since it was created, starting at 1. The version of a nonexistent or deleted key is 0.
A client opens a watcher to observe updates on a given key range.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.