文档
- Introduction
-
Concepts
- Architecture
-
Key Features
- Horizontal Scalability
- MySQL Compatible Syntax
- Replicate from and to MySQL
- Distributed Transactions with Strong Consistency
- Cloud Native Architecture
- Minimize ETL with HTAP
- Fault Tolerance & Recovery with Raft
- Automatic Rebalancing
- Deployment and Orchestration with Ansible, Kubernetes, Docker
- JSON Support
- Spark Integration
- Read Historical Data Without Restoring from Backup
- Fast Import and Restore of Data
- Hybrid of Column and Row Storage
- SQL Plan Management
- Open Source
- Online Schema Changes
- How-to
-
Reference
-
SQL
- MySQL Compatibility
- SQL Language Structure
- Data Types
-
Functions and Operators
- Function and Operator Reference
- Type Conversion in Expression Evaluation
- Operators
- Control Flow Functions
- String Functions
- Numeric Functions and Operators
- Date and Time Functions
- Bit Functions and Operators
- Cast Functions and Operators
- Encryption and Compression Functions
- Information Functions
- JSON Functions
- Aggregate (GROUP BY) Functions
- Window Functions
- Miscellaneous Functions
- Precision Math
-
SQL Statements
- `ADD COLUMN`
- `ADD INDEX`
- `ADMIN`
- `ALTER DATABASE`
- `ALTER TABLE`
- `ALTER USER`
- `ANALYZE TABLE`
- `BEGIN`
- `COMMIT`
- `CREATE DATABASE`
- `CREATE INDEX`
- `CREATE TABLE LIKE`
- `CREATE TABLE`
- `CREATE USER`
- `CREATE VIEW`
- `DEALLOCATE`
- `DELETE`
- `DESC`
- `DESCRIBE`
- `DO`
- `DROP COLUMN`
- `DROP DATABASE`
- `DROP INDEX`
- `DROP TABLE`
- `DROP USER`
- `DROP VIEW`
- `EXECUTE`
- `EXPLAIN ANALYZE`
- `EXPLAIN`
- `FLUSH PRIVILEGES`
- `FLUSH STATUS`
- `FLUSH TABLES`
- `GRANT <privileges>`
- `INSERT`
- `KILL [TIDB]`
- `LOAD DATA`
- `MODIFY COLUMN`
- `PREPARE`
- `RECOVER TABLE`
- `RENAME INDEX`
- `RENAME TABLE`
- `REPLACE`
- `REVOKE <privileges>`
- `ROLLBACK`
- `SELECT`
- `SET [NAMES|CHARACTER SET]`
- `SET PASSWORD`
- `SET TRANSACTION`
- `SET [GLOBAL|SESSION] <variable>`
- `SHOW CHARACTER SET`
- `SHOW COLLATION`
- `SHOW [FULL] COLUMNS FROM`
- `SHOW CREATE TABLE`
- `SHOW CREATE USER`
- `SHOW DATABASES`
- `SHOW ENGINES`
- `SHOW ERRORS`
- `SHOW [FULL] FIELDS FROM`
- `SHOW GRANTS`
- `SHOW INDEXES [FROM|IN]`
- `SHOW INDEX [FROM|IN]`
- `SHOW KEYS [FROM|IN]`
- `SHOW PRIVILEGES`
- `SHOW [FULL] PROCESSSLIST`
- `SHOW SCHEMAS`
- `SHOW [FULL] TABLES`
- `SHOW TABLE REGIONS`
- `SHOW TABLE STATUS`
- `SHOW [GLOBAL|SESSION] VARIABLES`
- `SHOW WARNINGS`
- `SPLIT REGION`
- `START TRANSACTION`
- `TRACE`
- `TRUNCATE`
- `UPDATE`
- `USE`
- Constraints
- Generated Columns
- Partitioning
- Character Set
- SQL Mode
- Views
- Configuration
- Security
- Transactions
- System Databases
- Errors Codes
- Supported Client Drivers
- Garbage Collection (GC)
- Performance
- Key Monitoring Metrics
- Alert Rules
- Best Practices
- TiSpark
- TiDB Binlog
- Tools
-
SQL
- TiDB in Kubernetes
- FAQs
- Support
- Contribute
- Adopters
- Roadmap
- Releases
Check the TiDB Cluster Status Using SQL Statements
TiDB offers some SQL statements and system tables to check the TiDB cluster status.
The INFORMATION_SCHEMA system database offers system tables as follows to query the cluster status and diagnose common cluster issues:
TABLESTIDB_INDEXESANALYZE_STATUSTIDB_HOT_REGIONSTIKV_STORE_STATUSTIKV_REGION_STATUSTIKV_REGION_PEERS
You can also use the following statements to obtain some useful information for troubleshooting and querying the TiDB cluster status.
ADMIN SHOW DDL: obtains the ID of TiDB with theDDL ownerrole andIP:PORT.- The feature of
SHOW ANALYZE STATUSis the same with that of theANALYZE_STATUStable. - Specific
EXPLAINstatementsEXPLAIN ANALYZE: obtains some detailed information for execution of a SQL statement.EXPLAIN FOR CONNECTION: obtains the execution plan for the query executed last in a connection. Can be used along withSHOW PROCESSLIST.- For more information about
EXPLAIN, see Understand the Query Execution Plan.
"Check the TiDB Cluster Status Using SQL Statements"
was last updated
Sep 17 2019:
*: update all anchor links to github style (#1515) (041e600)