PolarDB allows you to restart nodes. When the number of database connections reaches the upper limit or the database performance is compromised, you can manually restart nodes.
- A read/write splitting connection that is established after a read-only node is restarted forwards requests to the read-only node. If a read/write splitting connection is established before a read-only node is restarted, the connection does not forward requests to the read-only node. You can restart your application to close the read/write splitting connection and establish the connection again.
- During the restart, services may be interrupted for up to 1 minute. We recommend that you perform this operation during off-peak hours and make sure that your application is configured to automatically reconnect to the database service.
- The time required to restart a node depends on the data volume. Several hours may be required to restart a node. Proceed with caution.
- Log on to the PolarDB console.
- In the upper-left corner of the console, select the region where the cluster that you want to manage is deployed.
- Find the cluster that you want to manage and click the cluster ID.
- In the upper-right corner of the Database Nodes section for the Overview page, click the icon to switch the display mode.
- Find the node that you want to restart, and click Restart in the Actions column. Note If your cluster version is PolarDB for MySQL 8.0, you can set the innodb_fast_startup parameter to ON to accelerate the restart process. For more information about how to change parameter values, see Specify cluster parameters.
- In the dialog box that appears, click OK.
Related API operations
|RestartDBNode||Restarts a node of a PolarDB cluster.|