- Newest
- Most votes
- Most comments
Response from the support
I would like to mention that the rds proxy connection get closed after 24 hours is expected behavior. RDS Proxy won't close connection when there is ongoing transaction. But once the transaction is completed and the database connection age has passed 24 hours, it will be added to the termination queue.
Soon it will be closed again where its not within a transaction. When 24 hrs time is reached, the proxy checks if the client connection is in transaction. If so, the proxy waits at most 15 more mins. If after 15 mins the client connections is still in transaction, then proxy would drop the client connection regardless." .This is expected behavior due to architectural design which is similar in Aurora serverless.
"Aurora Serverless v1 closes connections that are older than 24 hours." [+] https://aws.amazon.com/blogs/database/best-practices-for-working-with-amazon-aurora-serverless/
As you are looking for more clarification about the below in the documentation above mentioned is not updated in our public documentation, but will be updated soon. As this is required to undergo a change process, I am not in a position to provide the ETA on when the document will be updated.
TL;DR: the doc is not clear, we will fix it
Hi, Can you explain in a comment to my question why it is important for your use case to maintain connection open for such a long time? Why is a reconnection an issue in this use case?
Best,
Didier
Relevant content
- asked 4 months ago
- asked a year ago
- asked 10 months ago
- asked 5 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
Our infrastructure is based on Java microservices, each microservice is an independent processes without an application servers, messages are passed through queues. I need that connection remain always active, any process that remains active for an extended period has the same requirement; it doesn't seem like an isolated use case to me