Community journal

The latest from the MySQL community

Ideas, releases, practical guides, and perspectives from the people building with MySQL.

Follow the feed
Showing entries 1 to 10 of 59 « Previous | Next »
Displaying posts with tag: Amazon Aurora (reset)
Fix Amazon Aurora MySQL error 63955: Virtual index ID overflow

Your Amazon Aurora MySQL cluster looks healthy. Reads and writes succeed and every metric is green. Then a routine CREATE INDEX fails with error 63955, and from then on no index that includes a virtual column can be created on the cluster until you rebuild its databases.

Error Code: 63955. 
Index cannot be created because virtual index ID limit (4294967295) was reached.
  • What it means: the cluster has used up the internal IDs Aurora MySQL uses when it evaluates indexes that contain a virtual column. This error does not affect existing data or ordinary indexes, but new indexes on VIRTUAL generated columns, functional indexes, and multi-valued indexes fail.
  • What helps short term: converting the generated column in the failing index from VIRTUAL to STORED, so that the index no longer contains a …
[Read more]
Refresh a single tenant across accounts with Aurora MySQL and Amazon S3

Multi-tenant software as a service (SaaS) applications regularly need to copy one tenant’s data from production into a lower environment. Teams do this to reproduce a defect, validate a schema change, or give quality assurance (QA) a representative dataset. When production and non-production run in separate AWS accounts, their virtual private clouds (VPCs) often have no route to each other. That turns the copy into a networking problem as much as a data problem, and security teams are rightly reluctant to open a path between the two.

In this post, we show how to move a single tenant’s data between Amazon Aurora MySQL-Compatible Edition clusters in two separate AWS accounts, using Aurora cloning, SELECT INTO OUTFILE S3, and LOAD DATA FROM S3. The databases don’t connect directly. Each account reaches Amazon Simple Storage Service (Amazon S3) independently through its own gateway VPC endpoint, and the accounts …

[Read more]
Help prevent out-of-memory restarts on Aurora MySQL 8.4

When an Amazon Aurora MySQL-Compatible Edition instance runs critically low on memory, the operating system terminates the mysql process. This drops every connection, rolls back in-flight transactions, and triggers a cluster restart. The instinctive fixes (move to a larger instance, or lower max_connections) treat the symptom, not the underlying memory pressure your workload generates.

Aurora has long included out-of-memory (OOM) avoidance that watches system memory and takes recovery actions before the OS steps in. On Aurora MySQL version 3, use the aurora_oom_response parameter to configure these actions; Aurora provides sensible defaults that you can customize. Aurora MySQL version 8.4 adds a new instance-level …

[Read more]
Diagnose Amazon Aurora MySQL performance using CloudWatch Database Insights

When an Amazon Aurora MySQL-Compatible Edition or Amazon Relational Database Service (Amazon RDS) for MySQL database slows down, it can be hard to tell why. CPU graphs and slow-query logs rarely tell the whole story. The more direct answer usually lies in wait events. A wait event tells you what your sessions are waiting for: reading from storage, redo log flushes, acquiring an internal lock, or waiting for CPU time. Amazon CloudWatch Database Insights surfaces this data as DB load, so you can quickly see whether a database is constrained and, if so, on what.

Earlier MySQL wait-event guidance relied on the Performance Insights dashboard. Our 2018 post …

[Read more]
AWS contributes a large-transaction binary log optimization to MySQL

When MySQL commits a large transaction carrying gigabytes of changes, writing it to the binary log (binlog) can freeze every other commit on the server for minutes. This includes transactions that touch unrelated data. This bottleneck is detrimental to applications that depend on low commit latency. On October 29, 2026, AWS shipped an optimization into community MySQL that removes this bottleneck. We call it Binary Log Optimization for Large Transactions (BOLT). It has been available in Amazon Aurora MySQL since v1.22.0 and in all currently supported major versions (Aurora MySQL 2.x, 3.x, and 8.4.x), where it’s always on for every customer. BOLT is planned to be released as part of a future MySQL innovation release.

BOLT provides …

[Read more]
Using Blue/Green Deployment For (near) Zero-Downtime Primary Key Updates in RDS MySQL

Large tables can pose challenges for many operations when working with a database. Occasionally, we may need to modify the table definition. Since RDS replication does not use asynchronous for its replication, the typical switchover procedure is not feasible. However, the Blue/Green feature of RDS utilizes asynchronous replication, which allows us to update the table […]

Aurora vs RDS: How to Choose the Right AWS Database Solution

This post was originally published in July 2018 and was updated in July 2023.

Now that Database-as-a-service (DBaaS) is in high demand, there are multiple questions regarding AWS services that cannot always be answered easily: When should I use Aurora and when should I use RDS MySQL?  What are the differences between Aurora and RDS? How do I choose which one to use?

In this blog, we will answer all of these important questions and provide a general overview comparing the two database services, Aurora vs RDS.

Understanding DBaaS

DBaaS cloud services allow users to use databases without configuring physical hardware and infrastructure or installing software. But …

[Read more]
Failover comparison in Aurora MySQL 2.10.0 using proxySQL vs Aurora's cluster endpoint

Aurora cluster promises a high availability solution and seamless failover procedure. However, how much is actually the downtime when a failover happens? And ho

A First Glance at Amazon Aurora Serverless RDS

If you often deploy services in the cloud, you certainly, at least once, forgot to stop a test instance. I am like you and I forgot my share of these. Another mistake I do once in a while is to provision a bigger instance than needed, just in case, and forget to downsize it. While this is true for compute instances, it is especially true for database instances. Over time, this situation ends up adding a cost premium. In this post, we’ll discuss a solution to mitigate these extra costs, the use of the RDS Aurora Serverless service.

What is Amazon Aurora Serverless?

Since last spring, Amazon unveiled a new database related product: RDS Aurora Serverless. The aim of this new product is to simplify the management around Aurora clusters. It brings a likely benefit for the end users, better control over cost. Here are some …

[Read more]
Amazon Aurora Multi-Primary First Impression

For what reason should I use a real multi-primary setup?

To be clear, not a multi-writer solution where any node can become the active writer in case of needs, as for Percona XtraDB Cluster (PXC) or Percona Server for MySQL using Group_replication. No, we are talking about a multi-primary setup where I can write at the same time on multiple nodes. I want to insist on this “why?”.

After having excluded the possible solutions mentioned above, both covering the famous 99.995% availability, which is 26.30 minutes of downtime in a year, what is left?

Disaster Recovery? Well, that is something I would love to have, but to be a real DR solution we need to put several kilometers (miles for imperial) in the middle.

And we know …

[Read more]
« Previous | Next »