etcd
An open-source distributed key-value store based on the Raft consensus algorithm, commonly used for service discovery, configuration management, and distributed coordination.
Core Facts
Milvus integrates ETCD for metadata management and service discovery, uses message middleware such as Kafka or Pulsar to handle log streams, and its object storage supports Amazon object storage, MinIO and various cloud storages.
etcd is the core data store for Kubernetes and uses Raft to guarantee strong consistency of cluster configuration data
Docker、Kubernetes、Terraform、etcd、Prometheus等云原生核心项目几乎都用Go编写
Timeline (last 90 days)
Milvus integrates ETCD for metadata management and service discovery, uses message middleware such as Kafka or Pulsar to handle log streams, and its object storage supports Amazon object storage, MinIO and various cloud storages.
etcd is a CNCF graduated project with a mature community and broad ecosystem integration.
etcd's transactions support version-number-based CAS (compare-and-swap) semantics, which is the key to implementing optimistic concurrency control.
Distributed locks are usually implemented using etcd's transactions (Txn) and leases: a client checks in a transaction whether a key does not exist (by comparing the version number to 0), and if so writes and binds a lease, thereby atomically acquiring the lock; the lock holder must keep renewing, and after a crash the lease expires and the lock is automatically released.
Kubernetes uses etcd to store the state of all cluster objects, which is etcd's most well-known application.
etcd supports TLS-encrypted communication and role-based access control (RBAC), and also provides comprehensive monitoring metrics and backup and recovery tools.
watch is implemented based on etcd's MVCC (multi-version concurrency control): each modification generates a new revision number, and clients can specify a revision to start watching from, thereby supporting replay of historical events and no event loss after reconnection.
A lease is a TTL-based authorization mechanism in etcd: a client applies for a lease and binds several keys to it, and must renew it periodically (keepalive); once the lease expires or the client loses contact, the bound keys are automatically deleted.
etcd provides HTTP/gRPC interfaces and supports key-value create, read, update, delete, watch, and lease mechanisms.
Raft guarantees strong consistency (linearizable reads and writes), while high availability depends on a majority of nodes being alive: when the cluster loses a majority of nodes, etcd rejects writes to protect consistency, which is a typical CP choice in the CAP trade-off.
22 more timeline events
All Facts (20)
Milvus integrates ETCD for metadata management and service discovery, uses message middleware such as Kafka or Pulsar to handle log streams, and its object storage supports Amazon object storage, MinIO and various cloud storages.
65%UnverifiedEvery write operation to etcd goes through Raft log replication where the Leader receives the request, replicates to a majority of Followers, and returns success after confirming the commit
90%UnverifiedMilvus架构中etcd承担分布式协调角色,存储集群元数据和节点状态
85%Partially Verifiedetcd is the core data store for Kubernetes and uses Raft to guarantee strong consistency of cluster configuration data
65%Partially VerifiedDocker、Kubernetes、Terraform、etcd、Prometheus等云原生核心项目几乎都用Go编写
65%Unverifiedetcd is a CNCF graduated project with a mature community and broad ecosystem integration.
50%Unverifiedetcd implements strong consistency based on the Raft consensus algorithm, ensuring that the cluster can still read and write normally as long as a majority of nodes are alive.
50%Unverifiedetcd recommends deploying an odd number of nodes (usually 3 or 5), because writes require confirmation from more than half of the nodes.
50%UnverifiedRaft and Paxos have similar goals but Raft is easier to implement in engineering, and etcd's raft library is reused by many projects.
50%UnverifiedRaft guarantees strong consistency (linearizable reads and writes), while high availability depends on a majority of nodes being alive: when the cluster loses a majority of nodes, etcd rejects writes to protect consistency, which is a typical CP choice in the CAP trade-off.
50%Unverifiedetcd provides HTTP/gRPC interfaces and supports key-value create, read, update, delete, watch, and lease mechanisms.
50%UnverifiedA lease is a TTL-based authorization mechanism in etcd: a client applies for a lease and binds several keys to it, and must renew it periodically (keepalive); once the lease expires or the client loses contact, the bound keys are automatically deleted.
50%Unverifiedwatch is implemented based on etcd's MVCC (multi-version concurrency control): each modification generates a new revision number, and clients can specify a revision to start watching from, thereby supporting replay of historical events and no event loss after reconnection.
50%Unverifiedetcd supports TLS-encrypted communication and role-based access control (RBAC), and also provides comprehensive monitoring metrics and backup and recovery tools.
50%UnverifiedKubernetes uses etcd to store the state of all cluster objects, which is etcd's most well-known application.
50%UnverifiedDistributed locks are usually implemented using etcd's transactions (Txn) and leases: a client checks in a transaction whether a key does not exist (by comparing the version number to 0), and if so writes and binds a lease, thereby atomically acquiring the lock; the lock holder must keep renewing, and after a crash the lease expires and the lock is automatically released.
50%Unverifiedetcd's transactions support version-number-based CAS (compare-and-swap) semantics, which is the key to implementing optimistic concurrency control.
50%UnverifiedIn systems such as Kubernetes, when etcd or the API Server is unavailable, Pods may still continue running on nodes, but users can no longer issue new instructions.
50%UnverifiedSystems such as etcd, Consul, and TiKV all use the Raft consensus algorithm.
50%UnverifiedIn distributed systems, equivalents of CAS include Redis's SET NX and etcd's compare-and-swap transaction.
50%