From 1af04edef35ec851d9b59e135fe5c85bc29a9b78 Mon Sep 17 00:00:00 2001 From: marsishandsome Date: Tue, 15 Jun 2021 18:02:11 +0800 Subject: [PATCH] address codereview Signed-off-by: marsishandsome --- content/docs/5.1/reference/architecture/overview.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/content/docs/5.1/reference/architecture/overview.md b/content/docs/5.1/reference/architecture/overview.md index 8e347af..997e52e 100644 --- a/content/docs/5.1/reference/architecture/overview.md +++ b/content/docs/5.1/reference/architecture/overview.md @@ -53,12 +53,16 @@ The TiKV placement driver is the cluster manager of TiKV, which periodically and ## Store -The **Store** is a TiKV instance. A Store stores multiple peers. There is a [RocksDB](https://rocksdb.org) database within each **Store** and it stores data into the local disk. +A **Store** refers to the storage node in the TiKV cluster (an instance of tikv-server). Each store has a corresponding TiKV instance. ## Region TiKV shards continuous ranges of keys into **Regions**, and replicates **Regions** via the Raft protocol. When data size increases until reaching a threshold, a Region will be split into multiple. Conversely, if the size of the Region shrinks due to data deletion, two adjacent Regions can be merged into one. +## Peer + +A replica of a Region is called a peer. Multiple peers of the same Region replicate data via the Raft consensus algorithm, so peers are also members of a Raft instance. + ## Node A TiKV **Store** is a physical node in the cluster, which could be a virtual machine, a container, etc. Within each Node, there can be one or more stores.