By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Aurora Serverless V2 repeatedly fails over because LSN couldn't advance

0

We recently migrated our production workload to Aurora MySQL and we've had the primary writer instance fail, triggering a fail over. The fail over triggers errors in our application as the connection pool attempts to maintain it's connection to the now defunct instance. The error in the logs is:

Attempting to restart the database with zero downtime because the last sequence number (LSN) couldn't advance.

Is this a misconfiguration or issue with Aurora Serverless V2? Searching for this error yielded no results.

Topics
ServerlessAnalyticsDatabase
Tags
ServerlessAmazon AuroraAurora MySQL
Language
English
e0steven
asked a year ago561 views
1 Answer
1

This error message, "Attempting to restart the database with zero downtime because the last sequence number (LSN) couldn't advance," suggests that the primary instance was unable to write new transactions to the database, leading to the failover.

If your application is generating a high volume of write operations that the database can't keep up with, you might see this error. You might need to adjust your workload, or consider scaling up your Aurora Serverless v2 capacity.

profile picture
EXPERT
Sedat Salman
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.

Guidelines for Answering Questions

Relevant content