What should I pay attention to when using RDS for MySQL?
1. The instance host information is invisible to you. Your applications can only access a database through the corresponding IP address and port.
2. After enabling an RDS for MySQL instance, basic operation and maintenance are not required for the database (such as high availability, security patches, etc.). However, you need to pay attention to the following indicators::
• The usage of CPU, IOPS, host space, and backup space of the MySQL instance, which should be changed or expanded if they are insufficient.
• Please check the MySQL instance for performance issues. For instance, whether there are a large number of slow SQLs, whether SQL statements need to be optimized, whether there are redundant or missing indexes, etc
What is the availability of an RDS for MySQL instance?
The availability of an RDS for MySQL instance can be calculated simply based on the following formula: Instance availability = (1-fault time/total service time)×100%.
Will my RDS for MySQL instance be affected by other users' instances?
No.
Your instance is isolated from other users' instances based on the tenant. You can only see the instances you have opened. Moreover, resources are isolated from each other and do not affect each other.
Does RDS for MySQL support cross-AZ high availability?
Yes. You can select the same AZ or different AZs to deploy your primary/standby instances.
Availability Zone (AZ) refers to the physical area in which the power and network are independent of each other within the same region. Some regions support multiple AZs, while others only support a single AZ.
For example, customers in the East China 1 resource pool can select any one or two of AZ 1, AZ 2, and AZ 3 when purchasing an RDS for MySQL primary/standby instances. These three AZs are interworking.
Can I change an RDS for MySQL primary/standby instance to a single instance?
No. However, you can change a single instance to a primary/standby instance through series upgrading.
To change a primary/standby instance to a single instance, you can use Data Transmission Service (DTS) to migrate primary/standby instances to single instances. DTS also supports the migration of single instances to primary/standby instances.
What should I do to resolve slow login to websites when using the RDS for MySQL?
To resolve this issue, it is recommended that you:
• Check the performance of the database instance through the console of RDS for MySQL instance.
• Troubleshoot this issue using the application by checking the current database connection status and comparing the differences between local databases and RDS for MySQL instances.
Can I configure data synchronization between primary instances and read-only instances?
No.
Changing the data synchronization mode displayed on the RDS for MySQL only involves the replication mode between the primary instance and the standby instance, excluding the read-only instance. The data replication mode can be changed in semi-synchronious and asynchronization. By default, the primary instance and read-only instance are replicated asynchronously.
What is the time delay for primary/standby synchronization?
If the primary instance has a heavy load for a certain period of time, i.e., executing a large number of transactions per second, replication to the standby instance may be delayed. Under normal circumstances, the delay is generally a few seconds.
The time delay for primary/standby replication is caused by several factors, mainly including:
• Network communication status.
• The transaction workload on the primary instance, i.e., the number of transactions executed on the primary instance per second.
• The size of the transactions executed on the host.
• Load of the standby instance and read-only instance.
Can multiple ECSs connect to the same RDS for MySQL instance?
The RDS for MySQL instance does not set relevant restriction rules. Multiple ECSs can connect to the same RDS DB instance as long as the workload limits of a database are not exceeded.
You can decide whether to connect multiple ECSs to the same instance depending on your service needs.
Does the newly enabled RDS for MySQL instance have a default account?
Yes. When enabling a database, you need to enter the root account and password. If you forget the root@% password set at the time you enabled the database, the system will generate an initial password for the account by default. In addition, you can reset the root@% account password on the console later.
Resetting Procedure: Find the instance to reset the password in the Instance Management list and click More > Modify Password to reset the root account password.
What is the encryption function supported by an RDS for MySQL instance?
The encryption function supported by the RDS for MySQL instance is the same as that on the official website. For details, see the official documentation.
What are the restrictions when GTID is enabled on RDS for MySQL?
By default, GTID is enabled on the RDS for MySQL instances and cannot be disabled because the cluster construction relies on GTID. If GTID is disabled, all functions of the instance (such as backup restoration, and master-slave switching) will be affected or become unavailable.
If GTID is enabled for MySQL community edition, an error will be reported when:
• Using a SELECT statement to create tables (for example: create table...select).
• Processing transactions engines that support transactions (InnoDB) and engines that do not support transactions (MyISAM) in a transaction at the same time.
• Creating temporary tables in an explicit transaction.
Will different RDS for MySQL instances share CPU and memory?
No, because the RDS for MySQL instance resources between different instances are isolated.
The database instances ordered for eSurfing Cloud users occupy CPU and memory separately, which are suitable for application scenarios that require high-performance stability, thus ensuring efficient and stable operation of services.
How many databases can run on an RDS for MySQL instance?
There are no limit rules on the number of databases that can run on an RDS for MySQL instance, which depends on the MySQL engines.
If the host CPU, memory, disk, and other system resources are sufficient, there are no limitations to the number of databases running on an instance. For details, see the MySQL official documentation.
Is RDS for MySQL compatible with MariaDB?
MariaDB is a branch of the MySQL source code. It is mainly maintained by the open-source community and uses GPL licensing.
MariaDB and MySQL are compatible for the most part. There is almost no difference for front-end applications (such as PHP, Perl, Python, Java,. NET, MyODBC, Ruby, and MySQL Connector).
Does RDS for MySQL support TokuDB?
Currently, the official MySQL does not support TokuDB.
RDS for MySQL does not support TokuDB, either.
Is there a maximum size allowed for a single table for RDS for MySQL instances?
The maximum size allowed for a single table for RDS for MySQL instances is not subject to the MySQL scheme but depends on the maximum file size of the operating system.
Due to some metadata overheads in the use of the database, the maximum size allowed for a single table is at a TB level.
How do I access an RDS for MySQL instance from a client?
If you access an RDS for MySQL instance through the ECS, the ECS and MySQL must be within the same VPC.
You can apply for an EIP and bind it to the corresponding database instance, use the EIP to access the database service locally, connect to the database through the MySQL client, and then create a database.
For details, see Introduction to Instance Connection Mode.
What are the billing modes of RDS for MySQL? What are the billing items?
RDS for MySQL has two billing modes:
• Payment by Volume.
• Annual/Monthly Package.
The billing items of RDS for MySQL include instance specifications, data storage capacity, and backup storage capacity. The instance specifications include VCPU and memory. MySQL provides data storage space to store your data, and the backup storage space is used to store your backup data. During subscription, the data storage space and the backup storage space are purchased based on the rate of 1:1, which can be scaled up separately. If object storage can be selected for the resource pool you are using, the billing items include the instance specifications, data storage capacity, and the capacity occupied by the instance in the object storage.
How are the RDS for MySQL instances in Payment by Volume mode billed?
For the RDS for MySQL instances in Payment by Volume mode, you can top up cash into your eSurfing Cloud account in advance with a balance of not less than CNY 100. Then, the system settles the account according to the actual usage. Hourly billing is based on natural hours (Beijing time). Less than an hour is counted as one hour. Fees are deducted from the cash balance of your account. It is recommended that you enable the service on the hour. Less than a natural hour is counted as one hour. If you delete the service in advance, the billing is also based on natural hours. For details about the deletion and charging rules, see Description of Payment by Volume.