100% CPU on Empty MySQL Instance

Jason Bennett 15 Reputation points
2024-04-01T23:18:33.1233333+00:00

Hello,

I recently setup an Azure mySQL Database. It is type Standard_B1s (small yes). I have not created any databases at all. The only thing in there is the default database mySQL comes with. There are no users, no-one connecting to it. Looking at the CPU metric, sometime yesterday the CPU hit 100% when I sleeping and has been lingering there for no apparent reason.

I checked "trx_rseg_history_len" and it came back 0. HLL = 0. There are no backups running and connected users is just me while troubleshooting and "azure_superuser" user

I can't figure out why the host CPU is 100% when I don't even have a database on it yet.

Any help appreciated.

Thanks

Azure Database for MySQL
Azure Database for MySQL
An Azure managed MySQL database service for app development and deployment.
850 questions
0 comments No comments
{count} vote

2 answers

Sort by: Most helpful
  1. Oury Ba-MSFT 19,581 Reputation points Microsoft Employee
    2024-04-01T23:47:59.4766667+00:00

    @Jason Bennett

    Thank you for reaching out.

    I would suggest to first review your workload and considering using a different tier from Standard_B1s if you need stable performance all the time:

    User's image

    Azure Database for MySQL - Flexible Server service tiers

    Regards,

    Oury


  2. RahulRandive 9,901 Reputation points
    2024-04-02T00:26:15.0366667+00:00

    Hi @Jason Bennett

    It's unusual to see a sudden spike in CPU usage on the Empty MySQL Flexible server. Please take a look at the document 'Troubleshoot high CPU utilization in Azure Database for MySQL - Flexible Server.'

    https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-troubleshoot-high-cpu-utilization

    It provides queries that can help you identify the current workload and any background processes that might be causing the issue.

    Thank You!


Your answer

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