Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Introduction to the overall architecture of TiDB

2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)06/01 Report--

The TiDB architecture diagram is as follows

The TiDB cluster is mainly divided into three components:

TiDB Server

TiDB Server is responsible for receiving SQL requests, processing SQL-related logic, finding the TiKV address for storing data needed for calculation through PD, and interacting with TiKV.

Get the data and finally return the result. TiDB Server is stateless, does not store data itself, is only responsible for computing, can be extended infinitely horizontally, and can be extended through the

Load balancer components, such as LVS, HAProxy or F5, provide a unified access address.

/ / analogy mongos or router server in MongoDB sharding cluster

PD Server

Placement Driver (PD for short) is the management module of the whole cluster, which has three main tasks: one is to store the meta-information of the cluster (where is a Key stored?

TiKV node); second, scheduling and load balancing of TiKV clusters (such as data migration, Raft group leader migration, etc.); third, global unique allocation

And incremental transaction ID.

PD is a cluster, and an odd number of nodes need to be deployed. Generally, it is recommended to deploy at least 3 nodes online.

/ / analogy of config server in MongoDB sharding cluster

TiKV Server

TiKV Server is responsible for storing data. From an external point of view, TiKV is a distributed Key-Value storage engine that provides transactions. The basic unit for storing data is

Region, each Region is responsible for storing the data of one Key Range (the left closed and right open interval from StartKey to EndKey), each TiKV

The node is responsible for multiple Region. TiKV uses Raft protocol for replication to maintain data consistency and disaster recovery. Copies are managed in units of Region

Multiple Region on different nodes form a Raft Group, which is a copy of each other. Load balancing of data among multiple TiKV is scheduled by PD

Here, scheduling is also carried out in Region units.

/ / analogy of replica set in MongoDB sharding cluster

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report