Timeout Parameters
The following table lists the RDS for MySQL timeout parameters.
Parameter |
Reboot Required |
Description |
---|---|---|
connect_timeout |
No |
Number of seconds that the mysqld server waits for a connection packet before responding with Bad handshake. If the network quality is poor, you can increase the value of this parameter. |
idle_readonly_transaction_timeout |
No |
Number of seconds that the server waits for idle read-only transactions before killing the connection. (Supported in versions later than 5.7.23) |
idle_transaction_timeout |
No |
Number of seconds that the server waits for idle transactions before killing the connection. If this parameter is set to the default value 0, connections are never killed. (Supported in versions later than 5.7.23) |
idle_write_transaction_timeout |
No |
Number of seconds that the server waits for idle read-write transactions before killing the connection. If this parameter is set to the default value 0, connections are never killed. (Supported in versions later than 5.7.23) |
innodb_lock_wait_timeout |
No |
Number of seconds an InnoDB transaction waits for a row lock before giving up. |
innodb_rollback_on_timeout |
Yes |
InnoDB rolls back only the last statement on a transaction timeout by default. If innodb_rollback_on_timeout is specified, a transaction timeout causes InnoDB to abort and roll back the entire transaction. |
lock_wait_timeout |
No |
Timeout in seconds for attempts to acquire metadata locks |
net_read_timeout |
No |
Number of seconds to wait for more data from a connection before aborting the read. |
net_write_timeout |
No |
Number of seconds to wait for a network packet to be written to a TCP connection before aborting the write. |
interactive_timeout |
No |
Number of seconds the server waits for activity on an interactive connection before closing it. |
wait_timeout |
No |
Number of seconds the server waits for activity on a noninteractive connection before closing it. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot