etcd-io/etcd

Distributed reliable key-value store for the most critical data of a distributed system

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 14 minutes ago
Added to GitGenius on April 7th, 2021
Created on July 6th, 2013
Open Issues & Pull Requests: 317 (+0)
Number of forks: 10,466
Total Stargazers: 52,165 (+0)
Total Subscribers: 1,265 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.8 hours
Mean response time: 75.7 days
90th percentile: 115.3 days
Tracked items: 930

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 68% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "area/tooling" is answered fastest, typically in under an hour, while "stage/tracked" waits about 7 days. Almost all tracked open issues have seen activity in the last three months. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 115
New in 7 days: 3
Closed in 7 days: 4
Avg open age: 430 days
Stale 30+ days: 75
Stale 90+ days: 25

Recent activity

Opened in 7 days: 3
Closed in 7 days: 4
Comments in 7 days: 9
Events in 7 days: 42

Top labels

  • type/feature (464)
  • stale (318)
  • type/bug (311)
  • help wanted (141)
  • area/robustness-testing (111)
  • area/testing (111)
  • stage/tracked (102)
  • area/security (78)

Detailed Description

etcd is a distributed reliable key-value store designed for the most critical data of a distributed system.

etcd solves the problem of maintaining consistent, highly-available state across multiple machines in a distributed system. It uses the Raft consensus algorithm to manage a replicated log, ensuring that data remains reliable even when nodes fail or become unreachable. The tool provides a simple gRPC API, automatic TLS encryption with optional client certificate authentication, and is benchmarked to handle ten thousand writes per second. Its design prioritizes both correctness and performance in scenarios where data loss or inconsistency would be catastrophic.

The tool suits projects that need a central source of truth for critical configuration, service discovery, or coordination data in distributed environments. It is particularly well-matched to infrastructure and cloud-native applications, and has seen production adoption across many companies. Teams should choose etcd when they require strong consistency guarantees and are willing to operate a clustered system; it is not appropriate for use cases where eventual consistency is acceptable or where operational complexity must be minimized. The project includes etcdctl, a command-line client for interacting with the store.

The project receives issue reports from both core maintainers and external users, indicating real-world adoption without an overwhelming support burden. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on feature development, bug fixes, and robustness testing, reflecting a focus on expanding capabilities while ensuring reliability through rigorous testing practices.