A company is running an Amazon RDS for MySQL Multi-AZ DB instance. The primary instance in us-east-1a experiences an unexpected failure. After the automatic failover, the application team reports that write latency has increased significantly. The new primary instance is in us-east-1b. The DB instance class and storage configuration are identical. What is the MOST likely cause of the increased write latency?
Trap 1: The DB instance class in us-east-1b is a different size than the…
The instance class and storage are identical.
Trap 2: The Multi-AZ configuration uses asynchronous replication, causing…
Multi-AZ uses synchronous replication.
Trap 3: The new primary is in the same Availability Zone as the…
Multi-AZ synchronous replication only occurs between primary and standby, not between primary and application.
- A
The DB instance class in us-east-1b is a different size than the original.
Why wrong: The instance class and storage are identical.
- B
The application is connecting to the DB instance in a different Availability Zone, increasing network latency.
The new primary is in us-east-1b, and if the application is in us-east-1a, cross-AZ latency increases write latency.
- C
The Multi-AZ configuration uses asynchronous replication, causing higher latency.
Why wrong: Multi-AZ uses synchronous replication.
- D
The new primary is in the same Availability Zone as the application, but the standby is in a different AZ, causing synchronous replication overhead.
Why wrong: Multi-AZ synchronous replication only occurs between primary and standby, not between primary and application.