| title | summary | category | aliases | |
|---|---|---|---|---|
Error Codes and Troubleshooting |
Learn about the error codes and solutions in TiDB. |
reference |
|
This document describes the problems encountered during the use of TiDB and provides the solutions.
TiDB is compatible with the error codes in MySQL, and in most cases returns the same error code as MySQL. In addition, TiDB has the following unique error codes:
| Error code | Description | Solution |
|---|---|---|
| 8001 | The memory used by the request exceeds the threshold limit for the TiDB memory usage. | Increase the value of the system variable with the tidb_mem_quota prefix. |
| 8002 | To guarantee consistency, a transaction with the SELECT FOR UPDATE statement cannot be retried when it encounters a commit conflict. TiDB rolls back the transaction and returns this error. |
Retry the failed transaction. |
| 8003 | If the data in a row is not consistent with the index when executing the ADMIN CHECK TABLE command, TiDB returns this error. |
|
| 8004 | A single transaction is too large. | See here for the cause and solution. |
| 8005 | Transactions in TiDB encounter write conflicts. | See here for the cause and solution. |
| 9001 | The PD request timed out. | Check the state/monitor/log of the PD server and the network between the TiDB server and the PD server. |
| 9002 | The TiKV request timed out. | Check the state/monitor/log of the TiKV server and the network between the TiDB server and the TiKV server. |
| 9003 | The TiKV server is busy and this usually occurs when the workload is too high. | Check the state/monitor/log of the TiKV server. |
| 9004 | This error occurs when a large number of transactional conflicts exist in the database. | Check the code of application. |
| 9005 | A certain Raft Group is not available, such as the number of replicas is not enough. This error usually occurs when the TiKV server is busy or the TiKV node is down. | Check the state/monitor/log of the TiKV server. |
| 9006 | The interval of GC Life Time is too short and the data that should be read by the long transactions might be cleared. | Extend the interval of GC Life Time. |
| 9500 | A single transaction is too large. | See here for the solution. |
| 9007 | Transactions in TiKV encounter write conflicts. | See here for the cause and solution. |
See the troubleshooting and FAQ documents.