Aurora MySQL database engine updates 2018-06-05 (version 1.17.3) (Deprecated) - Amazon Aurora
Improvements
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Aurora MySQL database engine updates 2018-06-05 (version 1.17.3) (Deprecated)

Version: 1.17.3

Aurora MySQL 1.17.3 is generally available. All new Aurora MySQL database clusters with MySQL 5.6 compatibility, including those restored from snapshots, will be created in Aurora MySQL 1.17.3. You have the option, but are not required, to upgrade existing database clusters to Aurora MySQL 1.17.3. You can create new database clusters in Aurora MySQL 1.14.4, Aurora MySQL 1.15.1, or Aurora MySQL 1.16. You can do so using the Amazon CLI or the Amazon RDS API and specifying the engine version.

With version 1.17.3 of Aurora MySQL, we are using a cluster patching model where all nodes in an Aurora DB cluster are patched at the same time.

Note

This version is currently not available in the Amazon GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. There will be a separate announcement once it is made available.

If you have any questions or concerns, Amazon Support is available on the community forums and through Amazon Support. For more information, see Maintaining an Amazon Aurora DB cluster in the Amazon Aurora User Guide.

Improvements

  • Fixed an issue where an Aurora Replica can restart when using optimistic cursor restores while reading records.

  • Fixed an issue where an Aurora Writer restarts when trying to kill a MySQL session (kill "<session id>") with performance schema enabled.

  • Fixed an issue where an Aurora Writer restarts when computing a threshold for garbage collection.

  • Fixed an issue where an Aurora Writer can occasionally restart when tracking Aurora Replica progress in log application.

  • Fixed an issue with the Query Cache when auto-commit is off and that could potentially cause stale reads.