MySQL Bugs: #109018: Improved failover for Amazon Aurora

Bug #109018	Improved failover for Amazon Aurora
Submitted:	7 Nov 2022 17:01	Modified:	10 Nov 2022 16:13
Reporter:	Dave Cramer (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	Connector / ODBC	Severity:	S4 (Feature request)
Version:	Amazon Aurora, 8.0	OS:	Other
Assigned to:		CPU Architecture:	Any (Amazon Aurora)

Description:
Currently when an Aurora cluster fails over the client has to wait for the DNS to update to reconnect to the writer which can take around 25 seconds. We (AWS Development) would like to contribute code to the MySQL ODBC driver to reduce that failover time from 25 Seconds to 5 Seconds.

How to repeat:
Connect to an Aurora write endpoint.
Cause the cluster to fail over
wait until the client can reconnect.

Suggested fix:
It is possible using aurora_replica_status to introspect the cluster and determine the new write instance before the DNS updates. We propose extensions to the ODBC driver to leverage this information.

To be clear we are proposing to do the work and contribute a patch

Thank you for the reasonable feature request.

Thank you very much for offering contribution, we appreciate it!
Please note that in order to submit contributions you must first sign the Oracle Contribution Agreement (OCA). Please send us a signed copy of the Oracle Contributor Agreement (OCA) as outlined in https://oca.opensource.oracle.com

Signing an OCA needs to be done only once and it's valid for all other Oracle governed Open Source projects as well.

Getting a signed/approved OCA on file will help us facilitate your contribution - this one, and others in the future.  

Please let me know, if you have any questions.

Thank you for your interest in MySQL.

Amazon already has a signed OCA. Do we have to do anything to add ourselves to that or is the current OCA sufficient.

What are the next steps ?

Hello Dave,

Thank you for the details.
IMHO if an employee is covered by company OCA then our community manager need to be informed by your company's responsible person(manager, legal, team lead…anyone who is set as a contact person on behalf of the company's signed OCA).  I'll let our community team manager know about this and update you soon on what needs to be done. Btw, one reason I can imagine in your case is that I see  you have reported this FR using personal email address instead of Amazon's which could be the reason you are not shown as OCA signed etc. In any case, I'll contact our community team manager on this and get back to you. Thank you.

Sincerely,
Umesh