Tair (Redis OSS-Compatible) cluster and read/write splitting instances route client requests through proxy nodes. If a proxy node experiences uneven connection distribution, high latency, or service disruption, restart or rebuild it to restore normal operation.
Restart mode comparison
| Mode | Effect | When to use |
|---|---|---|
| In-place Restart | Restarts the proxy process on the existing node | Connection imbalance or minor latency spikes |
| Rebuild Proxy | Replaces the proxy node entirely | In-place restart did not resolve the issue |
Start with In-place Restart. If the problem persists, use Rebuild Proxy.
Impact
Restarting or rebuilding proxy nodes may cause transient connections. Perform this operation during off-peak hours and make sure your application supports automatic reconnection.
Prerequisites
The instance must meet one of the following conditions:
A cluster instance in proxy mode
Restart or rebuild a proxy node
Log on to the console and go to the Instances page. In the top navigation bar, select the region in which the instance resides. Find the instance and click the instance ID.
In the left-side navigation pane, click Service Availability.
In the Proxy Node section, select the proxy nodes to restart or rebuild and click Batch Restart.
In the panel that appears, set Restart Mode:
In-place Restart: Restarts the proxy nodes.
Rebuild Proxy: Rebuilds the proxy nodes. Select this mode if an in-place restart did not resolve the issue.
Click OK.
Verify the result
After the operation completes, confirm that the proxy nodes function correctly:
On the Service Availability page, verify that the instance status returns to Running.
Check your application logs to confirm that client connections are re-established.
Monitor instance performance metrics to verify that latency and connection usage have improved. For more information, see View performance monitoring data.