BE
Refer to the link given by the proposed solution :
What events would cause Amazon RDS to initiate a failover to the standby replica?
Loss of availability in primary Availability Zone
Loss of network connectivity to primary
Compute unit failure on primary
Storage failure on primary
And
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html
The primary DB instance switches over automatically to the standby replica if any of the following conditions occur:
An Availability Zone outage
The primary DB instance fails
The DB instance's server type is changed
The operating system of the DB instance is undergoing software patching
A manual failover of the DB instance was initiated using Reboot with failover
B. A storage failure on the primary database.
If there is a storage failure on the primary database, it may become unavailable, leading to an automated failover to the standby replica. Amazon RDS continuously monitors the health of the database and performs automated failover to a standby replica in the event of a primary instance failure.
D. Database corruption errors.
If the primary database experiences database corruption errors, it may no longer be able to serve requests correctly. In this case, Amazon RDS will trigger an automated failover to the standby replica to maintain high availability and data integrity.
- The primary host of the RDS Multi-AZ instance is unhealthy.
- The RDS instance was modified by customer.
As per https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZSingleStandby.html
B - Storage failure caused Autimatic Failover
C - Write contention could put the database in hang state hence need automatic failover.
Not E: It needs manual failover not automated failover.
B for sure
E: https://aws.amazon.com/rds/features/multi-az/#:~:text=Failover%20conditions&text=Amazon%20RDS%20automatically%20performs%20a,Compute%20unit%20failure%20on%20primary
When operations such as DB Instance scaling or system upgrades like OS patching are initiated for Multi-AZ deployments, for enhanced availability, they are applied first on the standby prior to an automatic failover (see the Aurora documentation for details on update behavior). As a result, your availability impact is limited only to the time required for automatic failover to complete. Note that Amazon RDS Multi-AZ deployments do not failover automatically in response to database operations such as long running queries, deadlocks or database corruption errors.
B, Note that Amazon RDS Multi-AZ deployments do not fail over automatically in response to database operations such as long running queries, deadlocks or database corruption errors.
https://aws.amazon.com/rds/faqs/
E, The DB instance's server type is changed
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZ.html
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
kung07
Highly Voted 2 years, 9 months agoMrDEVOPS
Highly Voted 2 years, 9 months agoalbert_kuo
Most Recent 11 months, 2 weeks agoFinger41
2 years agowaterzhong
2 years agoablazleon
2 years, 3 months agoabhishek_m_86
2 years, 8 months agojackdryan
2 years, 8 months agoIftee
2 years, 8 months agoMegatonN
2 years, 8 months agomrbreeze
2 years, 8 months agobull2
2 years, 9 months agonicat
2 years, 9 months ago