Modifying RDS for MariaDB Instance Parameters
You can modify parameters in a custom parameter template to optimize RDS database performance. This section describes how to modify parameters of an RDS for MariaDB instance.
Precautions
- You can only change parameter values in custom parameter templates. You cannot change the parameter values in default parameter templates.
- Pay attention to the following points when configuring parameters in a parameter template:
- When you change a parameter value in a parameter template that has been applied to a DB instance and save the change, the change takes effect only to the DB instance and does not affect other DB instances.
- When you modify dynamic parameters on the Parameters page of a DB instance and save the modifications, the modifications take effect immediately regardless of the Effective upon Reboot setting. However, when you modify static parameters on the Parameters page of a DB instance and save the modifications, the modifications do not take effect until you manually reboot the DB instance.
- Modifying parameter template parameters: When you modify parameters in a custom parameter template on the Parameter Templates page and save the modifications, the modifications do not take effect until you have applied the template to your DB instances. When you modify static parameters in a custom parameter template on the Parameter Templates page and save the modifications, the modifications do not take effect until you have applied the template to your DB instances and manually rebooted those DB instances. For details, see Applying a Parameter Template.
- Improper parameter settings may have unintended consequences, including reduced performance and system instability. Exercise caution when modifying database parameters and you need to back up data before modifying parameters in a parameter template. Before applying parameter template changes to a production DB instance, you should try out these changes on a test DB instance.
- Global parameters must be modified on the console. Session-level parameters can be modified using SQL statements. When you modify a parameter, the time when the modification takes effect depends on the type of the parameter.
The RDS console displays the statuses of DB instances that the parameter template applies to. For example, if the DB instance has not yet used the latest modifications made to its parameter template, its status is Parameter change. Pending reboot. Manually reboot the DB instance for the latest modifications to take effect for that DB instance.
RDS has default parameter templates whose parameter values cannot be changed. You can view these parameter values by clicking the default parameter templates. If a custom parameter template is set incorrectly, the database startup may fail. If this happens, you can re-configure the custom parameter template based on the settings of the default parameter template.
Modifying a Custom Parameter Template and Applying It to DB Instances
- Log in to the management console.
- Click in the upper left corner of the page and choose Databases > Relational Database Service.
- In the navigation pane on the left, choose Parameter Templates.
- Choose Parameter Templates in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
- On the Parameters page, modify parameters as required.
Figure 1 Modifying parameters in a parameter template
- To save the modifications, click Save.
- To cancel the modifications, click Cancel.
- To preview the modifications, click Preview.
- After the parameter values are modified, you can click Change History to view the details.
- The modifications do not take effect until you apply the parameter template to your DB instances. For details, see Applying a Parameter Template.
- View the status of the DB instance to which the parameter template was applied.
If the DB instance status is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.
- The DB instance reboot caused by instance class changes will not make parameter modifications take effect.
- If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
- If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
Modifying Parameters of a DB Instance
- Log in to the management console.
- Click in the upper left corner of the page and choose Databases > Relational Database Service.
- On the Instances page, click the target DB instance.
- In the navigation pane, choose Parameters. On the displayed page, modify parameters as required.
Check the value in the Effective upon Reboot column.
- If the value is Yes and the DB instance status on the Instances page is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.
- If you have modified parameters of a primary DB instance, you need to reboot the primary DB instance for the modifications to take effect. (For primary/standby DB instances, the parameter modifications are also applied to the standby DB instance.)
- If you have modified parameters of a read replica, you need to reboot the read replica for the modifications to take effect.
- If the value is No, the modifications take effect immediately.
- To save the modifications, click Save.
- To cancel the modifications, click Cancel.
- To preview the modifications, click Preview.
After parameters are modified, you can click Change History to view parameter modification details.
- If the value is Yes and the DB instance status on the Instances page is Parameter change. Pending reboot, a reboot is required for the modifications to take effect.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot