Share via

How will Microsoft handle reports of "MySQL 8.0.38, 8.4.1 and 9.0.0 crashes on restart if database has 10K tables or more"

Pat Weisman 0 Reputation points
2024-07-17T18:22:01.78+00:00

My team is currently using Azure Database for MySQL Flexible Server and I've seen recent posts from Percona that there is is an unstable fix release 8.0.38 which is only a few fix release levels from our current environment. See:

My assumption is that Microsoft will postpone updates beyond 8.0.37 until this issue is subsequently resolved, but using the managed service means I don't control the maintenance updates. I don't see a specific published policy on how this is handled, but I could have easily enough missed related documentation.

Azure Database for MySQL
Azure Database for MySQL
An Azure managed MySQL database service for app development and deployment.
762 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Oury Ba-MSFT 17,791 Reputation points Microsoft Employee
    2024-07-17T21:34:21.3633333+00:00

    @Pat Weisman Thank you for reaching out with your concerns regarding the MySQL version updates.

    It’s reasonable to assume that Microsoft Azure would take into account stability issues when deciding which versions to support.

    Microsoft current version for Azure MYSQL Flexible server is 5.7 and 8. see doc for more info https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-supported-versions

    User's image

    For now, Microsoft Azure for MySQL supports until version 8.0.36 as you can see in the above table. we are postponing updates beyond version 8.0.37 (8.0.37 not included). The release of version 8.0.38 is not yet decided. The release of version 8.0.38 is not yet decided; it may possibly be in October, but that will depend on the stability of the version at that time.

    However, I would like to clarify that this decision is not due to Azure Database for MySQL being impacted by the reported bug. Our managed service enforces a limit of 1,000 table spaces loaded during startup, crash recovery, and scenarios involving a non-empty insert buffer (ibuf), which significantly lowers the risk associated with the bug mentioned in the versions you referred to. We will continue to monitor community feedback closely before officially releasing version 8.0.38.

    https://learn.microsoft.com/en-us/azure/mysql/concepts-version-policy

    Please don't forget to mark as accept answer if the reply was helpful.

    Regards,

    Oury