A user is using a small MySQL RDS DB. The user is experiencing high latency due to the Multi AZ feature.Which
of the below mentioned options may not help the user in this situation?
A.
Schedule the automated back up in non-working hours
B.
Use a large or higher size instance
C.
Use PIOPS
D.
Take a snapshot from standby Replica
Explanation:
An RDS DB instance which has enabled Multi AZ deployments may experience increased write and commit
latency compared to a Single AZ deployment, due to synchronous data replication. The user may also face
changes in latency if deployment fails over to the standby replica. For production workloads, AWS
recommends the user to use provisioned IOPS and DB instance classes (m1.large and larger. as they are
optimized for provisioned IOPS to give a fast, and consistent performance. With Multi AZ feature, the user can
not have option to take snapshot from replica.
D
d
All options make sense if MySQL 5.6 or after used.
Take database snapshot and perform Point in Time Recovery operation of a Read Replica (supported for MySQL 5.6)…..
You can now take database snapshots and perform Point in Time Recovery operations of a Read Replica in addition to performing these operations on a master database instance. When taking a database snapshot of a Single-AZ master instance, you may experience a brief I/O suspension. Taking a database snapshot from a Read Replica instead, can help you mitigate this brief performance impact. However, please note that the database snapshots taken from a Read Replica at a given time may not include all the transactions present on the master at that time because of possible replica lag.
Still, we can go with the option D, in order to have the consistent data when latency between the master and replica is more.
https://aws.amazon.com/about-aws/whats-new/2013/08/28/amazon-rds-read-replica-new-features/
d
With Multi AZ feature, the user can not have option to take snapshot from replica???
high latency due to multi AZ feature? Wtf?
Question is strange.
D