Tagged articles
TiKV
18 articles · Page 1 of 1
This article explains how TiDB's NewSQL architecture eliminates manual sharding by providing horizontal scaling, ACID transactions, and MySQL compatibility through a distributed architecture with TiKV storage, PD scheduling, and TiFlash for HTAP workloads.
Distributed DatabaseHTAPMySQL Compatibility
0 likes · 26 min read

This guide explains how to diagnose and fix TiKV disk‑space problems by identifying oversized log files, redundant space‑placeholder files, and excessive RocksDB/Titan data, offering command‑line checks, configuration tweaks such as enabling log rotation, disabling reserve space, and tuning GC and Titan discardable‑ratio to restore balanced storage.
ConfigurationStorageTiKV
0 likes · 16 min read

This article provides a comprehensive analysis of TiDB's PointGet operator, detailing its execution flow in the TiKV storage layer, including protobuf interfaces, read‑through lock handling, snapshot creation, MVCC logic, and the integration of the Titan plugin for large values.
Distributed DatabaseMVCCPointGet
0 likes · 20 min read

This article introduces the distributed transactional KV store TiKV, explains its role as TiDB’s storage engine, details its multi‑layered architecture and Raft‑based consistency model, and discusses the performance and resource challenges encountered at massive data scales along with the engineering solutions implemented to address them.
Distributed DatabaseRaftTiKV
0 likes · 14 min read

The article details a Redis‑compatible, disk‑based KV service built atop TiKV using a compute‑storage split (Tula), describes custom key encoding and expiration mechanisms, and explains four optimization stages that introduce slot‑based hashing and adaptive concurrency to dramatically cut garbage‑collection latency while preserving write performance.
KV storeRedis CompatibilityTiKV
0 likes · 21 min read

This article presents Ctrip's experience migrating over 2 PB of cold data to JuiceFS, detailing the system's architecture, metadata engine selection, extensive performance testing, fault‑tolerance analysis, and operational optimizations that reduced storage and maintenance costs while supporting future petabyte‑scale workloads.
Cold Data StorageJuiceFSTiKV
0 likes · 15 min read

This guide explains why a TiKV node remains pending offline after a scale‑out and scale‑in operation, walks through detailed log inspection, region checks, and command‑line troubleshooting, and provides a step‑by‑step solution to forcefully remove the problematic region and clean up the store.
ClusterTiDBTiKV
0 likes · 13 min read

This article walks through a real‑world TiDB/TiKV disk‑space alarm case, diagnosing why the GC worker got stuck, how TiCDC’s lingering changefeed caused outdated MVCC versions, and the step‑by‑step commands and monitoring tricks used to restore normal GC and reclaim storage.
GCTiCDCTiDB
0 likes · 15 min read

This article demonstrates how to simulate and recover TiKV cluster failures by shutting down one, two, or three nodes, explains the impact on Raft groups and region availability, and provides step‑by‑step commands for disabling PD scheduling, using tikv‑ctl, and restoring data integrity.
Cluster RecoveryPDRaft
0 likes · 28 min read

This article explains TiDB's HTAP architecture, covering industry challenges, the row‑store TiKV and column‑store TiFlash design, MPP integration in TiDB 5.0, and a range of real‑time use cases such as dashboards, reporting, and data‑warehouse pipelines.
Database ArchitectureHTAPMPP
0 likes · 16 min read

TiDB is a distributed, MySQL-compatible database built from three core components—TiDB Server for stateless SQL processing, PD for global scheduling and metadata management, and TiKV for high‑performance key‑value storage—coordinated via the Raft consensus algorithm to ensure strong consistency and fault tolerance.
Database ArchitecturePDRaft
0 likes · 13 min read

Percolator implements a two‑phase commit transaction protocol with a client coordinator, a timestamp oracle, and storage (Bigtable or TiKV’s RocksDB), providing snapshot‑isolated ACID semantics via lock, write, and data columns; TiKV adds parallel prewrite, short‑value storage, point‑read shortcuts, calculated commit timestamps, and single‑region one‑phase commits to boost performance while keeping the design simple and scalable, though high contention can cause retries and read‑wait delays.
PercolatorRocksDBTiKV
0 likes · 20 min read

This article explains the core components of TiDB—including TiKV Server, PD Server, and TiDB Server—their roles in storage, scheduling, and computation, and how the Raft consensus algorithm and TiSpark extension enable a reliable, scalable distributed database solution.
Distributed DatabaseHTAPPD
0 likes · 13 min read

This article introduces TiDB’s hybrid transactional‑analytical processing capabilities, explains TiKV’s region‑based storage built on RocksDB, and provides a detailed overview of RocksDB and LevelDB architectures, including their data structures, write‑read flows, and key optimizations for modern distributed database systems.
Distributed DatabaseHTAPKV storage
0 likes · 16 min read

This article provides a comprehensive overview of TiDB's architecture, detailing the roles of TiKV Server, Placement Driver (PD), TiDB Server, and the TiSpark component, and explains how Raft ensures data consistency across the distributed database system.
Distributed DatabasePlacement DriverRaft
0 likes · 11 min read

Meitu migrated its high‑traffic push‑service storage from fragmented Redis nodes to the TiKV‑based Titan system, using a dual‑write rollout, batch‑operation tuning, and TiKV configuration tweaks, achieving required QPS, cutting costs by about 60%, and delivering stable, maintainable service after six months.
Database MigrationPush ServiceTiKV
0 likes · 13 min read

This article explains how TiKV implements multi-version concurrency control (MVCC) on top of RocksDB and details its two‑phase commit transaction model, including Prewrite and Commit phases, Percolator‑style optimizations, lock handling, conflict resolution, and garbage‑collection strategies.
MVCCPercolatorRocksDB
0 likes · 14 min read

This article explains why the PingCAP team selected Rust over Go, C++, and Java for the TiKV storage layer, introduces Rust's core concepts such as ownership, borrowing, lifetimes, and thread safety, and shares practical tips, tooling, and lessons learned from real‑world Rust development.
RustSystems ProgrammingTiKV
0 likes · 19 min read
