Skip to content

Need help for MySQL Upgrade from RDS Aurora MySQL 5.7 (2.11.0) to MySQL 8.0 default version

0

Hi Team,

We upgraded the .Net framework from 4.5.1 to 4.5.2 to be compatible with both MySQL 5.7 & MySQL 8.0 as we are in the process of upgrading our database from the current Aurora MySQL 5.7 '2.11.0' to 8.0.

Post .netframework upgrade, getting database connectivity errors which are given below.

Error From Application Log: 2025-02-14 04:59:39Z [ces\UliSupport\Src\DataBase.cs 3705 ] ProcessException [Warning] [Unk ] CAUGHT: Error (None) opening database connection.MySql.Data.MySqlClient.MySqlException (0x80004005): Reading from the stream has failed. ---> System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

Error From MySQL: 2025-02-14T05:03:30.529142Z 162519 [Note] Aborted connection 162519 to db: 'unconnected' user: 'unauthenticated' host: '10.0.33.29' (Bad handshake) 2025-02-14T05:04:00.572654Z 162582 [Note] Aborted connection 162582 to db: 'unconnected' user: 'unauthenticated' host: '10.0.35.200' (Got an error writing communication packets) 2025-02-14T05:04:00.572677Z 162593 [Note] Aborted connection 162593 to db: 'unconnected' user: 'unauthenticated' host: '10.0.35.200' (Got an error writing communication packets) 2025-02-14T05:04:00.572660Z 164943 [Note] Aborted connection 164943 to db: 'unconnected' user: 'unauthenticated' host: '10.0.33.29' (Got an error reading communication packets)

Could someone help with this issue. Thanks in advance.

Regards, Sharique

1 Answer
0

The issues you're experiencing seem to be related to connectivity problems between your application and the Aurora MySQL database, rather than directly related to the upgrade process from MySQL 5.7 to 8.0. However, it's important to note that upgrading between major versions of MySQL requires careful planning and testing.

For the specific errors you're seeing:

  1. The application log error suggests a problem with establishing or maintaining a connection to the database. This could be due to network issues, firewall settings, or misconfigurations in the connection string.

  2. The MySQL errors indicate failed connection attempts, including bad handshakes and errors in communication packets. These could be caused by incompatibilities between the MySQL client library version in your .NET application and the MySQL server version, or by network-related issues.

To address these issues and proceed with your upgrade, consider the following steps:

  1. Verify that your .NET MySQL connector is compatible with both MySQL 5.7 and 8.0. You may need to update to the latest version of the connector.

  2. Check your application's connection string to ensure it's correctly configured for the Aurora MySQL endpoint.

  3. Review network configurations, including security groups and firewall rules, to ensure proper connectivity between your application and the database.

  4. Test the connection using a simple command-line tool or MySQL Workbench to isolate whether the issue is specific to your application or a general connectivity problem.

  5. Before proceeding with the upgrade, run the pre-upgrade checks provided by Amazon RDS. These checks can identify potential compatibility issues that need to be addressed before the upgrade.

  6. Consider using Amazon RDS Blue/Green Deployments for the upgrade process, as this method can minimize application downtime and provide a safer upgrade path.

  7. After addressing connectivity issues, thoroughly test your application with both MySQL 5.7 and 8.0 compatible Aurora clusters to ensure compatibility and proper functionality.

Remember that upgrading between major versions of MySQL can uncover incompatibilities in SQL syntax, stored procedures, or application code. It's crucial to review the MySQL 8.0 documentation for changes that might affect your application and to conduct comprehensive testing before and after the upgrade.
Sources
Amazon Aurora MySQL version 2 (with MySQL 5.7 compatibility) to version 3 (with MySQL 8.0 compatibility) upgrade checklist, Part 1 | AWS Database Blog
Troubleshooting for Aurora MySQL in-place upgrade - Amazon Aurora

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.