Share via

Unable to change MySQL tier to burstable after upgrading 8.4

Jason Chapman 0 Reputation points
2025-10-10T02:42:29.94+00:00

I recently upgrade MySql (used for Wordpress) from 5.7 to 8 and then 8.4. Burtstable was used when at version 5.7. I changed it General for the upgrade. When trying to change the tier back to burstable, it fails no mater which compute size I choose. Currently on East US.

$ az mysql flexible-server update --resource-group xyz-rg --name xyz-mysql-db-server --tier Burstable --sku-name Standard_B2s IOPS is 360 which is either your input or free(maximum) IOPS supported for your storage size and SKU. (InternalServerError) An unexpected error occured while processing the request. Tracking ID: '43f268f4-edfa-4b89-8fe9-be9cbeb8b64c'

Azure Database for MySQL

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Abhisek Mishra 845 Reputation points Microsoft External Staff Moderator
    2025-10-10T04:51:05.8333333+00:00

    Hi Jason Chapman,

    Welcome to the Microsoft Q&A and thank you for posting your questions here.

    Major version upgrades are resource-intensive, demanding significant CPU and memory. Burstable SKU instances, being credit-based, might struggle under these requirements, potentially causing the upgrade process to fail. Therefore, when upgrading a Burstable SKU, the system first upgrades the compute tier to a General-Purpose SKU to ensure sufficient resources are available for the upgrade.

    After the upgrade, a choice is prompted to decide whether to retain the General Purpose SKU or revert to Burstable SKU. Based on your pre-upgrade decision, the system either retains the General Purpose SKU or automatically reverts to Burstable SKU after the upgrade.

    Please confirm the pre-upgrade choice that you had made and share the details requested over private message.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.