![]() ![]() Applications that connect to a cloud service such as Azure Database for MySQL should expect transient errors and implement retry logic to handle these errors instead of surfacing these as application errors to users.Check the Microsoft Azure Service Dashboard for any known outages that occurred during the time in which the errors were reported by the application.Steps to resolve transient connectivity issues Some events can occasionally take longer to mitigate, such as when a large transaction causes a long-running recovery. However, your application loses its connection to the server for a short period of time of typically less than 60 seconds at most. The Azure Database for MySQL service has built-in high availability and is designed to mitigate these types of problems automatically. Transient errors occur when maintenance is performed, the system encounters an error with the hardware or software, or you change the vCores or service tier of your server. Persistent or non-transient errors (errors that regularly recur).Transient errors (short-lived or intermittent).Generally, connection issues to Azure Database for MySQL can be classified as follows: ![]() The compute allocation of the server is changed by scaling the number of vCores or moving to a different service tier.Maintenance being performed in the service.Issues with the infrastructure of the service.Maximum limit reached on some Azure Database for MySQL resources.For more information about migrating to Azure Database for MySQL - Flexible Server, see What's happening to Azure Database for MySQL Single Server?Ĭonnection problems may be caused by a variety of things, including: We strongly recommend for you to upgrade to Azure Database for MySQL - Flexible Server. Azure Database for MySQL - Single Server is on the retirement path. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |