Aurora MySQL database engine updates 2021-10-21 (version 2.10.1) - Amazon Aurora

Aurora MySQL database engine updates 2021-10-21 (version 2.10.1)

Version: 2.10.1

Aurora MySQL 2.10.1 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7, and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

Currently supported Aurora MySQL releases are 1.14.*, 1.15.*, 1.16.*, 1.17.*, 1.18.*, 1.19.*, 1.20.*, 1.21.*, 1.22.*, 1.23.*, 2.01.*, 2.02.*, 2.03.*, 2.04.*, 2.05.*, 2.06.*, 2.07.*, 2.08.*, 2.09.*, and 2.10.*.

You can upgrade an existing Aurora MySQL 2.* database cluster to Aurora MySQL 2.10.1. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.10.1. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.10.1.

To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the Amazon RDS API.

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

Note

For information on how to upgrade your Aurora MySQL database cluster, see Upgrading the minor version or patch level of an Aurora MySQL DB cluster.

Improvements

Security fixes:

Availability improvements:

  • Added the ability to cleanly shut down the cluster for future major version upgrades.

General improvements:

  • Fixed an issue that can cause high CPU consumption on the reader instances due to excessive logging of informational messages in internal diagnostic log files.

  • Fixed an issue where the value of a TIMESTAMP column of an existing row is updated to the latest timestamp when all of the following conditions are satisfied:

    1. A trigger exists for the table.

    2. An INSERT is performed on the table that has an ON DUPLICATE KEY UPDATE clause.

    3. The inserted row causes a duplicate value violation in a UNIQUE index or PRIMARY KEY.

    4. One or more columns are of TIMESTAMP data type and have a default value of CURRENT_TIMESTAMP.

  • Fixed an issue introduced in version 2.10.0 which causes use of json_merge function to raise an error code in certain cases. In particular, when json_merge function is used in a DDL containing generated columns, it can return error code 1305.

  • Fixed an issue where, in rare conditions, read replicas restarts when a large object's update history is being validated for a transaction's read view on the read replica.

  • Fixed an issue which, in rare conditions, causes a writer instance to restart when an in-memory data- integrity check fails.

Integration of MySQL community edition bug fixes

  • CURRENT_TIMESTAMP PRODUCES ZEROS IN TRIGGER. (Bug #25209512)

Comparison with Aurora MySQL version 1

The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).

MySQL 5.7 compatibility

This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:

  • Group replication plugin

  • Increased page size

  • InnoDB buffer pool loading at startup

  • InnoDB full-text parser plugin

  • Multisource replication

  • Online buffer pool resizing

  • Password validation plugin

  • Query rewrite plugins

  • Replication filtering

  • The CREATE TABLESPACE SQL statement