tikv/pd

Placement driver for TiKV

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

tikv/pd has 1k+ stars and 750+ forks on GitHub, is written in Go, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 20 minutes ago
Type:Server / PlatformCategory(s):NoSQL, Key-Value & CachesDatabases & Storage
Added to GitGenius on October 15th, 2026
Created on March 7th, 2016
Open Issues & Pull Requests: 1,016 (+0)
GitHub issues: Enabled
Number of forks: 787
Total Stargazers: 1,160 (+0)
Total Subscribers: 78 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.9 hours
Mean response time: 43.3 days
90th percentile: 84.2 days
Tracked items: 686

Maintainer activity

13 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in two opened in the past year never receives a reply. 51% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "severity/major" is answered fastest, typically in under an hour, while "type/ci" waits about 3 days. 63% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. 64% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 341
New in 7 days: 7
Closed in 7 days: 6
Avg open age: 393 days
Stale 30+ days: 296
Stale 90+ days: 250

Recent activity

Opened in 7 days: 7
Closed in 7 days: 6
Comments in 7 days: 2
Events in 7 days: 20

Top labels

  • type/bug (366)
  • type/enhancement (354)
  • type/ci (224)
  • affects-8.5 (194)
  • severity/major (188)
  • contribution (150)
  • type/development (122)
  • affects-8.1 (113)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

PD is a placement driver and cluster manager for TiKV, the distributed key-value store.

PD solves the problem of coordinating and scheduling a distributed TiKV cluster. It manages cluster topology, data placement, and scheduling decisions across nodes. The tool embeds etcd to provide fault tolerance and consensus, ensuring that cluster state remains consistent even when individual nodes fail. PD exposes an HTTP API for querying cluster membership and state, and provides command-line tools for administration and recovery.

PD is essential if you are deploying TiKV as a distributed storage system. It is a required component rather than an optional add-on; TiKV clusters cannot function without a running PD instance. The tool can be deployed as a single node for development or testing, or as a multi-node cluster for production use. PD integrates with the broader TiKV ecosystem, which includes TiDB for SQL access and TiUP for cluster deployment automation. Docker images are available for containerized deployments, and Kubernetes support is documented for cloud-native environments.

The project maintains active development with regular updates to its codebase. Contributions are actively solicited through documented contribution guidelines and a contribution map. The build process is straightforward, requiring only Go and a make invocation to produce the server binary, control utility, and recovery tool.