Storage management
Updated at:
This topic describes the storage management feature.
- storage managementFrom the basic information page of your database, click in the left navigation pane to change specifications, add read-only instances, release instances, or set a read policy for your dedicated RDS instances.
- To configure read/write splitting, click Set Read Policy to the right of the desired RDS instance. In the dialog box, select a read policy, configure the read/write weights, and then click OK. For more information about how read/write splitting works, see read/write splitting.
Note
- On the Capacity Management page, you set read/write weights for each RDS instance. If a PolarDB-X 1.0 database contains multiple RDS instances, you must set the read/write weights for each one.
- Before you release an RDS read-only instance, you must set its read weight to 0 in the PolarDB-X 1.0 console. Otherwise, PolarDB-X 1.0 continues to route traffic to the read-only instance, causing the release to fail.
- You configure read/write splitting at the PolarDB-X 1.0 database level. If multiple PolarDB-X 1.0 databases use the same RDS read-only instance, you must set its read weight to 0 in each of these PolarDB-X 1.0 databases.
- After you complete the configuration, connect to PolarDB-X 1.0 and run the SHOW NODE command to view the actual read traffic distribution.
mysql> show node; | ID | NAME | MASTER_READ_COUNT | SLAVE_READ_COUNT | MASTER_READ_PERCENT | SLAVE_READ_PERCENT | | 0 | xxx | 1 | 0 | 100% | 0% | | 1 | xxx | 0 | 0 | 0% | 0% | | 2 | xxx | 0 | 0 | 0% | 0% | | 3 | xxx | 0 | 0 | 0% | 0% | | 4 | xxx | 0 | 0 | 0% | 0% | | 5 | xxx | 0 | 0 | 0% | 0% | | 6 | xxx | 0 | 0 | 0% | 0% | | 7 | xxx | 0 | 0 | 0% | 0% | 8 rows in set (0.01 sec)
Is this page helpful?