Sep 15, 2021 · Databases

Percolator Distributed Transaction Architecture and Its Implementation in TiKV

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

Percolator Distributed Transaction Architecture and Its Implementation in TiKV

dbaplus Community

May 20, 2016 · Databases

Inside TiKV: MVCC Mechanics and Distributed Transaction Design

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.

Distributed TransactionsGarbage CollectionMVCC

0 likes · 14 min read

Inside TiKV: MVCC Mechanics and Distributed Transaction Design