Discussion on the performance Test of Mysql's High availability / disaster recovery Architecture

This article mainly introduces the performance testing discussion of Mysql's high availability / disaster recovery architecture, hoping to add and update some knowledge. If you have any other questions to know, you can continue to follow my updated article in the industry information.

The high availability / disaster recovery of the system is a topic of great concern to the system operation and maintenance personnel.

What highly available architecture designs can we do for the database based on the AWS cloud platform?

At present, there are two independent Region in Beijing and Ningxia in China. With regard to RDS, not only can Multi-AZ be set up, but AWS also supports RDS's cross-Region master-slave synchronization.

Today, we will discuss the performance testing of Mysql-based high availability / disaster recovery architecture.

1. Create Replica Slave

two。 Here we can choose to create Replica slave to "Beijing region" or "Ningxia region".

3. Due to the distance between Beijing and Ningxia, everyone will be concerned about the synchronization of Beijing Master and Ningxia Replica, will the network delay lead to a larger lag?

I'm going to test it today to see how much impact network latency will have on master-slave synchronization.

(note: there is no direct connection between Beijing region and Ningxia region, that is, cross-Region data synchronization of customers' EC2 or other services can only be transmitted through the public network or their own direct connect. But inside AWS, dedicated lines are provided for master-slave synchronization of RDS and Cross Region Replication function of S3, and a certain amount of bandwidth is provided for each account)

Test environment preparation