Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Relational Database Service/ User Guide/ Working with RDS for MySQL/ Parameters/ Modifying Parameters of an RDS for MySQL Instance

Modifying Parameters of an RDS for MySQL Instance

Updated on 2024-10-14 GMT+08:00

You can change parameter values in a custom parameter template and apply it to optimize RDS database performance.

You can only change the values in custom parameter templates. You cannot change the values in default parameter templates.

Keep in mind the following points before modifying the parameters:

  • Modifying instance parameters: If 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, if 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: If 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 apply the template to your DB instances. If 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 apply the template to your DB instances and manually reboot those DB instances. For details, see Applying a Parameter Template.

Global parameters can only be modified on the console. Session-level parameters can be modified using SQL statements. When you modify a parameter, the time when modifications take effect varies with the parameter type.

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. You need to manually reboot the DB instance for the latest modifications to take effect for that DB instance.

NOTE:

For better parameter modification experience, you are advised to upgrade the minor version of your DB instance to the latest.

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 with incorrect settings is applied to a DB instance, this instance may fail to start. 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 a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
  4. Choose Parameter Templates in the navigation pane on the left. On the Custom Templates page, click the target parameter template.
  5. On the Parameters page, modify parameters as required.

    For parameter details, see Suggestions on RDS for MySQL Parameter Tuning.

    Available operations are as follows:

    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.
      Figure 2 Previewing changes

  6. Click Change History to view the changes.
  7. Apply the parameter template to your DB instance. For details, see Applying a Parameter Template.
  8. View the status of the DB instance to which the parameter template has been applied.

    If the DB instance status is Parameter change. Pending reboot, you need to reboot the DB instance 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

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
  4. On the Instances page, click the DB instance name.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, modify parameters as required.

    NOTICE:
    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.
    Figure 3 Parameters

    • 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.

Modifying Parameters of Multiple DB Instances at a Time

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
  4. On the Instances page, select the DB instances with the same DB engine of the same version and choose More > Modify Parameters above the DB instance list.
  5. On the Modify Parameters page, select the parameters you want to modify, change the parameter values, and click Apply.

    A maximum of 30 parameters can be modified at a time. Only selected parameters will be applied to your DB instances. The modified parameters are automatically selected. You can also deselect them.

    NOTICE:
    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.
    Figure 4 Modifying parameters

  6. In the displayed dialog box, click OK.

    Figure 5 Confirming parameter changes

  7. After the parameters are modified, click the Parameter Changes tab on the Parameter Templates page to view details about the modified parameters.

Viewing Parameter Change History of a DB Instance

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
  4. On the Instances page, click the target instance name.
  5. In the navigation pane on the left, choose Parameters. On the displayed page, click Change History.

    You can view the parameter change history within a specified period (no more than two years). By default, the parameter change history of the last seven days is queried.

    Figure 6 Viewing parameter change history

    You can view the parameter names, original parameter values, new parameter values, modification statuses, modification time, application statuses, and application time.

Viewing Change History of a Parameter Template

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
  4. In the navigation pane, choose Parameter Templates. On the Custom Templates page, click the target parameter template.
  5. On the displayed page, choose Change History in the navigation pane.

    You can view the parameter change history within a specified period (no more than two years). By default, the parameter change history of the last seven days is queried.

    Figure 7 Viewing parameter change history

    You can view the parameter names, original parameter values, new parameter values, modification statuses, and modification time.

    You can apply the parameter template to DB instances as required by referring to Applying a Parameter Template.

Viewing Parameter Changes

  1. Log in to the management console.
  2. Click in the upper left corner and select a region.
  3. Click in the upper left corner of the page and choose Databases > Relational Database Service.
  4. On the Parameter Templates page, click the Parameter Changes tab.
  5. Click View Details in the Operation column.

    You can view detailed information about the modified parameters.

Common Parameters

Table 1 Common parameters

Parameter

Description

Reference

time_zone

The time zone. Keep the value of this parameter for read replicas the same as that for the primary instance.

How Can I Change the Time Zone?

default_password_lifetime

The global automatic password expiration policy, in days.

How Do I Configure a Password Expiration Policy for RDS for MySQL DB Instances?

tx_isolation

The default transaction isolation level.

How Do I Change the RDS Transaction Isolation Level?

character_set_server

The server character set.

How Do I Use the utf8mb4 Character Set to Store Emojis in an RDS for MySQL DB Instance?

lower_case_table_names

The case sensitivity of table names. If this parameter is set to 0, table names are stored as specified and are case sensitive. If it is set to 1, table names are stored in lowercase and are case insensitive.

How Do I Set Case Sensitivity for RDS for MySQL Table Names?

group_concat_max_len

The maximum permitted result length in bytes for the GROUP_CONCAT() function.

Incorrect GROUP_CONCAT Results

max_connections

The maximum number of concurrent client connections. If this parameter is set to default, the parameter value depends on how much memory there is.

What Is the Maximum Number of Connections to an RDS DB Instance?

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback