AWS announces AWS Interconnect – multicloud (preview), providing simple, resilient, high-speed private connections to other cloud service providers. AWS Interconnect - multicloud is easy to configure and provides high-speed, resilient connectivity with dedicated bandwidth, enabling customers to interconnect AWS networking services such as AWS Transit Gateway, AWS Cloud WAN, and Amazon VPC to other cloud service providers with ease.
How do I troubleshoot performance and connectivity issues with my Aurora PostgreSQL-Compatible read replicas?
I want to troubleshoot replica lag, connection issues, or failovers with my Amazon Aurora PostgreSQL-Compatible Edition read replicas.
Resolution
Identify and resolve replication lag
Replication lag occurs when there's a delay between write operations on the primary instance. Although Aurora PostgreSQL-Compatible instances in a database (DB) cluster share a storage volume with minimal replica lag, lag can still occur.
To monitor replica lag, see Monitoring Aurora PostgreSQL replication.
Manage idle connections
A significant number of idle database connections can cause performance issues and resource exhaustion.
To resolve these issues, identify and troubleshoot your slow-running queries.
Resolve failover-related configuration issues
Aurora’s PostgreSQL-Compatible automatic failover mechanism prioritizes high availability and might not maintain specific instance configurations. After a failover event, reader and writer instances might swap instance classes.
To check for failover events, complete the following steps:
- Open the Amazon Relational Database Service (Amazon RDS) console.
- In the navigation pane, choose Clusters, and then select your Aurora cluster.
- Choose Logs & events.
- Review the logs for recent failover events.
Identify the current primary instance in the Amazon RDS console to check whether the instance swapped instance classes and is now the writer instance.
To restore the configuration, you must manually initiate a failover.
Complete the following steps:
- Open the Amazon RDS console.
- In the navigation pane, choose Clusters, and then select your Aurora cluster.
- Choose Actions, and then choose Failover.
- Select an instance to become the new primary.
- Change the writer instance to the larger instance class and the reader instance to the smaller instance class.
To prevent configuration issues after future failovers, take one or more of the following actions:
- Set up Amazon CloudWatch alarms to monitor for failover events.
- Subscribe to an Amazon RDS event notification to receive notifications when failovers occur.
Note: You must grant Amazon RDS permissions to publish notifications to an Amazon Simple Notification Service (Amazon SNS) topic. - Invoke AWS Lambda functions that automatically adjust instance sizes after a failover event.
- Set up AWS Systems Manager Automation to create workflows that restore your configuration.
For an another failover solution, see How a large financial AWS customer implemented high availability and fast disaster recovery for Amazon Aurora PostgreSQL using Global Database and Amazon RDS Proxy.
Use the Aurora PostgreSQL read availability feature
Use the Aurora PostgreSQL-Compatible read availability feature to improve read availability when writer instance issues occur. The feature is available by default on Aurora PostgreSQL versions 16.1+, 15.2+, 14.7+, 13.10+, and 12.14+.
For more information, see Improving the read availability of Aurora Replicas.
Related information
Best practices with Amazon Aurora PostgreSQL
High availability for Amazon Aurora
- Topics
- Database
- Language
- English
Relevant content
- asked 2 years ago
