百度智能云

All Product Document

          Relational Database Service

          Change Configuration

          Considerations

          Before the change of configuration, specifications, which are supported by the current availability zone at present, are optional due to the dynamic change of resources in the availability zone.

          Master instance

          Master instance of dual-computer high-availability version

          Master instance's configuration change falls into two stages:

          • Date migration: there is no influence on the instance access, migration rate is directly proportional to data size. Herein, the data migration rate is 100G/h, and the migration time can be assessed according to the data size.
          • Instance switching: to ensure the data consistency, writing stop takes place during the switching stage, and the stop time is contingent upon the service traffic. Please select the low peak of service, avoid massive data change, and ensure there is a reconnection mechanism for services.

          Master instance of the standalone basic version

          Master instance's configuration change includes only one stage:

          • Instance switching: to ensure the data consistency, writing stop takes place during the switching stage, and the stop time is contingent upon the service traffic. Please select the low peak of service, avoid massive data change, and ensure there is a reconnection mechanism for services.

          Read-only instance

          Read-only instance's configuration change stages are the same as the master instance's. But:

          • Before the change of configuration, you need to disable read-only instance's read traffic. Do not enable the read traffic until the change of configuration is completed.
          • During the change of configuration:

            • a. Copy based on GTID ensures data consistency. During the copy, the closing of the instance does not take place.
            • b. The instance is unavailable, and master-slave delay may take place, so the use of instance is not recommended.

          Proxy instance

          During the change of configuration of proxy instance, only the number of nodes is changed, and data copy does not take place. For this reason, there is no influence on services during the change.

          Action

          1. Select an instance and click the name to enter the "Basic Information" page of instance details. In the "Configuration Information" module, click "Configuration Change".

          image.png

          1. Enter the "Configuration Change" page, on which the current configuration of the instance is displayed, and users can select memory and storage disk for changed instance.

          Notes:

          • RDS supports settings of configuration downgrading to memory, so memory can be adjusted according to your own needs.
          • Postpaid instance supports the configuration downgrading to memory, but prepaid instance does not support this action for now.
          • Proxy instance does not support this action for now.
          • Read-only instance's configuration downgrading needs to be operated independently.

          image.png

          1. Click the "Next" button to enter the "Confirm Order" page, where you can view the changed instance configuration.
          2. After confirming, click the "Go to pay" button at the lower right corner. Then, the system shows the "Payment" page, on which you can confirm the payment and complete the order. You can view the order by clicking "View Order Details" or click "Management Console" to enter the "RDS Instance List". The system updates RDS instance at the back end. After a successful change, you receive the information "Successfully change RDS instance".
          3. Enter the "RDS - Instance List" to view, and the RDS instance's status is shown as "Upgrading". After the change, the status is restored into "Running".
          Previous
          Data Replication Method
          Next
          Restart and Release