- Green versionView
- Green versionView
- Green versionView
- Green versionView
TiDBversionSoftware introduction
The official version of TiDB is an open source distributed SQL database. The official version of TiDB can help users complete functions such as adding, deleting, and modifying databases, allowing users to better manage data. The database has rich features such as horizontal scalability, cloud native, minimized ETL, high availability, and high consistency, providing users with a more simplified and convenient operation process.
TiDBversionSoftware function
Horizontal scalability
TiDB official version can expand SQL processing and storage simply by adding new nodes. This makes infrastructure capacity planning simpler and more cost-effective than traditional relational databases that only scale up.
MySQL compatible syntax
TiDB official version is like it is the MySQL 5.7 server for the application. You can continue to use all existing MySQL client libraries, and in many cases you don't need to change a single line of code in your application. Because TiDB is built from scratch and is not a MySQL fork, please review the list of known compatibility differences.
Distributed transactions with high consistency
TiDB internally shards the table into small range-based chunks, which we call "regions". The default size of each region is approximately 100MiB, and TiDB uses two-phase commit internally to ensure that regions are maintained in a transactionally consistent manner.
Cloud native
TiDB is designed to work in public, private or hybrid clouds, simplifying deployment, provisioning, operations and maintenance.
TiDB’s storage layer, called TiKV, became a Cloud Computing Native Foundation member project in 2018. The TiDB platform’s architecture also allows SQL processing and storage to scale independently of each other in a very cloud-friendly way.
Minimize ETL
TiDB is designed to support transaction processing (OLTP) and analytical processing (OLAP) workloads. This means that while you may have traditionally done transaction processing on MySQL and then extracted, transformed, and loaded (ETL) the data into a column store for analytical processing, this step is no longer required.
High availability
TiDB uses the Raft consensus algorithm to ensure that data is highly available and securely replicated across storage in Raft groups. If a failure occurs, the Raft group will automatically elect a new leader for the failed member and automatically repair the TiDB cluster without any manual intervention. Failures and self-healing operations are also transparent to applications.
TiDBversionSoftware FAQ
The client reports Region is Unavailable error
Reason: The Region is unavailable for a period of time, possibly because the TiKV server is busy, the request is returned by TiKV (such as not leader or epoch not match), the request to TiKV times out, etc.
Solution: TiDB will perform backoff retry internally. If the backoff time exceeds a certain threshold (default 20s), an error will be reported. You can check the TiKV server status to ensure cluster health.
TiKV server is busy error
Cause: TiKV internal flow control mechanism triggered.
Solution: Check the TiKV load situation, optimize query statements, and avoid writing or reading large batches of data.
Multiple TiKV cannot be started or there is insufficient memory
Cause: It may be insufficient hardware resources or incorrect configuration.
Solution: Increase hardware resources, check and adjust the TiKV configuration file, and ensure reasonable memory allocation.
TiDBversionSoftware update log
1. Fixed several bugs;
2. Optimize details;
Huajun editor recommends:
TiDB is a software that is completely fool-proof and super simple to operate. I also recommend it.SQL Server automatic installer,Data Loader,SQLyog,access tools,DBeaverDownload and use related software.
Useful
Useful
Useful