TiKV Best Practices
summary
TiKV is a Rust database that uses Raft + RocksDB to deliver horizontal scalability, high availability and externally-consistent transactions; the talk covers concrete ops: PD detects hot read/write regions, splits small regions, and automates leader transfer and replica balancing across racks and DCs, with a store lifecycle (offline → tombstone) to avoid data loss during scale in. Practical tuning includes thread-pool sizing, RocksDB compression and block cache tweaks, and monitoring metrics that reveal CPU, disk I/O or apply stalls.
AI-written summary · about
chapters (20)
- 0:00Intro
- 2:08TIKV Overview and History
- 6:56Architecture
- 12:25st Part: Theories
- 13:29The topology of a TIKV cluster
- 18:503.1 Scale - Transfer leader
- 20:27Ecosystem
- 20:462rd Part: Practices
- 22:421.2 Deployment - Cross IDC
- 23:521.3 Demployment - Configurations
- 24:532.1 Scale - Add new nodes
- 25:582.2 Scale - Remove old nodes
- 28:373.1 Fight with hotspot
- 29:253.2 Fight with hotspots - Good design
- 30:213.4 Fight with hotspots - Find write hotspot
- 31:033.5 Fight with hotspot - Find read hotspot
- 34:173.6 Fight with hotspot - Auto balancing based
- 35:413.7 Fight with hotspot - Manual balance
- 37:064.1 Performance tuning - Find bottlenecks
- 39:244.3 Performance tuning . Read in RocksDB
related talks
40mTiKV Best Practices
11mAdapting TiKV for Cloud Storage
29mHow We Make TiKV- a Distributed Storage, More Cost-Effective On the Cloud
24mUsing a Distributed Key-Value Store
33mProvisioning the Distributed Database TiDB on Kubernetes
29mDistributed SQL How TiDB Modernized Data Management
49mThe Paradigm Shift - Understanding the Move To Distributed Databases
29mDistributed SQL: How TiDB Modernized Data Management