RDS for MySQL provides an overload protection feature to prevent system breakdowns caused by sudden traffic surges to the primary node when read-only or secondary nodes collectively fail.

Precautions

If the connection endpoint for your instance does not have the overload protection feature, upgrade the instance's kernel minor version. For information about how to upgrade the kernel minor version of the instance, refer to Manually upgrading instance kernel minor versions.

The overload protection feature takes effect only when the Read/Write separation feature is enabled for the connection endpoint, and the primary node is not the only node in the endpoint.

Only proxy endpoints support the overload protection feature.

Required

An instance has been created and the state of the instance is Running. For specific steps, refer to Create instance.

Procedure

Log on to the RDS for MySQL console.

In the upper-left corner of the top menu bar, select the project and region for the instance.

tip

If the project to which the instance belongs is not set, this operation should select the project as All resources.

In the left navigation bar, choose MySQL \> Instance list.

On the Instances page, click the target instance name.

At the top of the page, click the Connectivity tab.

On the Connectivity page, in the Endpoints list, click Edit in the Actions column for the target connection endpoint to open the Modify endpoint page.

In the Advanced configuration area on the Modify endpoint page, enable or disable overload protection and click OK.

tip

When enabling overload protection, you must set a protection duration. After the set protection duration, the overload limit on the Primary node is removed. The overload protection duration ranges from 60 to 7,200s.

Last updated: 2025.08.15 18:32:41

Public security network record in Beijing: No. 11010802032137