Azure MySQL database stuck in restarting state.

Question

DB had connectivity problems, tried restart and it stuck.

Answer 1

Hello sheik dawood

Please be informed that Burstable compute is for workloads that stay idle or below baseline most of the time. If CPU runs near or above baseline for long periods, credits deplete and the server might become unreachable.

The burstable compute tier is designed for nonproduction workloads like development, staging, or testing environments and hence does not qualify for 24/7 support or root cause analysis (RCA).

Also, as you are unable to restore the server due to capacity issue, we have allowed you to restore now to the source server region North Central US.
https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-service-tiers-storage#service-tiers-size-and-server-types

I kindly request you to please check and confirm if your original server is working fine or not.

Answer 2

How long is the expected wait time in self heal or Azure infrastructure to recover?

Answer 3

If your Azure Database for MySQL is stuck in a restarting state, you may want to consider using the Self-Heal feature, which is designed to help resolve common server issues independently. This feature allows you to perform a one-click repair to restore service health quickly and safely.

To access Self-Heal:

1. Navigate to your MySQL server in the Azure portal.
2. Select Help from the left-hand menu.
3. Click Self Heal and choose the appropriate action.

Keep in mind that the Self-Heal feature may involve brief server downtime, especially if addressing availability-related issues. If the server remains unresponsive, you may need to wait for the Azure infrastructure to recover or consider reaching out to Azure support for further assistance.

---

References:

• Self-Heal in Azure Database for MySQL (Public Preview)
• Troubleshoot connection issues to Azure Database for MySQL - Flexible Server