Azure Database for PostgreSQL - Flexible Server unavailable twice a day

Question

We are running Azure Database for PostgreSQL - Flexible Server. According to the metrics, the system is not under heavy load at all (memory is constantly at approx. 60%, CPU 12% with no peaks). Database is not available approx. twice a day - this problem is documented in the Activity log of the Resource as Health event (details: "An unexpected problem is preventing restoring access to your Azure Database for PostgreSQL - Flexible server. We are working on resolving the problem."). The problem lasts for couple of minutes - and of course disrupts all requests made to our application.

Is there any way to report this problem to Microsoft (we don't have support plan for Technical assistance)? Do you have any idea, what can be done to fix this problem?

Thank you for the assistance.

Answer 1

Hi @Martin Gubis,

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue :

While running Azure Database for PostgreSQL - Flexible Server, the metrics show that the system is not under heavy load, memory is at 60% and CPU is at 12%. The database is unavailable, and this issue is recorded twice daily in the Activity log of the Resource as Health event. The issue occurs for a few minutes and disrupts all requests in an application.

Solution :

The issue was caused by excessive memory consumption. When too many connections were made to the database, it overwhelmed a service responsible for managing connections not the database server itself. To resolve this, upgrade the memory accordingly and limit the number of connections from the application server.

Please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

Answer 2

It was indeed the problem with the amount of memory consumed. When there were too many connections to database, consumed memory wrecked machine (although not database server, just some service responsible for connections). Had to upgrade to 4GB of memory and limit amount of connections from app server.