Things to know about using RDS

Things to know about using RDS

1, the RDS instance upgrade needs to notice the matter

RDS will have a maximum of 30 seconds of connection flash in the process of instance upgrade, you need to be prepared in advance, and set up the program with RDS Automatic reconnection, to avoid because the upgrade of the flash caused your service is not available.

2. The risk of RDS switching between inside and outside networks

RDS in the process of switching between internal and external network will appear the server and RDS connection disconnect, after the switch is completed please update the program's connection address, while switching the internal and external network will cause IP address changes.

3, the RDS rollback risk notice

Currently RDS supports data rollback, rollback is for the entire instance, single table libraries are not supported, and important data is backed up before rollback to avoid data loss after rollback is complete. If only some of the tables or portions of the data need to be rolled back, we recommend that you restore the data by creating a temporary instance, and then returning the required data from the staging instance to the production library after the temporary instance is created successfully.

4. Guidelines for RDS Lockout strategies

RDS has a locking mechanism, if your instance storage is full, your instance will be locked, the instance will become read-only after it is locked, it is recommended to check storage space usage periodically, and you can also set up a space-consuming SMS alert in the RDS console.

5. RDS Failover

RDS uses a master-and-standby high-availability mode, and RDS switches to standby in 30 seconds when the main library fails. There is (less than or equal to) 30 seconds of non-access during the switchover process, which requires you to set up a program to automatically re-connect with RDS, to avoid the switchover that causes your service to be unavailable.

6, RDS for MySQL data synchronization mode notice

The data synchronization between the RDS for MySQL 5.1 Primary and standby uses asynchronous mode with high performance in asynchronous mode, but the disadvantage is that there is a certain probability that the data inconsistency between the primary and the standby will occur.

The data synchronization between the RDS for MySQL 5.5 primary and standby uses a semi-synchronous mode in which write performance degrades, but the advantage is that the probability of inconsistent primary and standby data is greatly reduced. If you have very high data reliability requirements (such as financial systems), it is recommended that you purchase over 5.5 (inclusive) versions of RDS for MySQL.

The data synchronization between the RDS for MySQL 5.6 Primary and Standby uses the new MySQL 5.6 feature Gtid, which guarantees performance and ensures consistent master-and-standby data.

7. What else do you need to do after you purchase RDS?

After you purchase an RDS instance, you do not need to do the basic operations of the database (such as high availability, backup, security patches, etc.), but you also need to focus on the following things:

1) Whether your RDS instance has enough CPU, IOPS, space, connections, or not enough to optimize or upgrade.

2) Is there a performance problem with your RDS instance, whether there are a large number of slow sql,sql statements that need to be optimized, whether there are redundant indexes or missing indexes, etc.

3) If there is a SQL injection warning for your RDS instance, it is possible that your database could be hacked by a hacker SQL injection and you need to modify your application to avoid SQL injection attacks.

Source: >  

From for notes (Wiz)

Things to know about using RDS