PolarDB lets you manually restart a node in the console to resolve database connection and performance issues.
Notes
After a read-only node is restarted, new read-write splitting connections will forward requests to that node. Connections established before the restart are not affected. To forward requests from existing connections to the restarted node, you must restart your application.
A transient disconnection of less than one minute may occur during the restart. Restart the node during off-peak hours and ensure your application has a reconnection mechanism.
The time required to restart a node depends on your data volume and may take several hours. Proceed with caution.
Procedure
PolarDB for PostgreSQL (Centralized) cluster
Log on to the PolarDB console. In the navigation pane on the left, click Clusters. Select the region where the destination cluster is located, and then click the ID of the destination cluster to open the cluster product page.
On the Basic Information page, in the Database Nodes section, click the
icon in the upper-right corner to switch the view.Find the destination node and click Restart in the Actions column.
In the dialog box that appears, click OK.
PolarDB for PostgreSQL (Distributed) cluster
Log on to the PolarDB console. In the navigation pane on the left, click Clusters. Select the region where the destination cluster is located, and then click the ID of the destination cluster to open the cluster product page.
On the Basic Information page, in the Cluster Topology section, find the destination node. The location of the Restart button varies based on the view:
Detailed View: Click Restart in the upper-right corner of the node.
List View: Click Restart in the Actions column.
In the dialog box that appears, click OK.
Related API operations
API | Description |
Restarts a database node. |