Bug #100760 | MySQL 8.0.21 empty running instance, but the CPU load is abnormally high | ||
---|---|---|---|
Submitted: | 7 Sep 2020 13:05 | Modified: | 8 Sep 2020 8:53 |
Reporter: | Ye Jinrong | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S2 (Serious) |
Version: | 8.0.21 | OS: | CentOS (CentOS Linux release 7.8.2003 (Core)) |
Assigned to: | MySQL Verification Team | CPU Architecture: | x86 (Intel(R) Xeon(R) Platinum 8255C CPU @ 2.50GHz) |
[7 Sep 2020 13:05]
Ye Jinrong
[7 Sep 2020 13:06]
Ye Jinrong
show engine innodb status output
Attachment: innodb-status-31458.log (application/octet-stream, text), 9.11 KiB.
[7 Sep 2020 13:50]
Ye Jinrong
find which threads cause the cpu so hight ``` [root@yejr-mgr1 data01]# pidstat -t -p 31458 ... 09:49:05 PM 1000 - 31481 3.53 3.47 0.00 7.00 1 |__mysqld 09:49:05 PM 1000 - 31482 1.79 2.30 0.00 4.09 2 |__mysqld 09:49:05 PM 1000 - 31483 1.79 2.29 0.00 4.08 3 |__mysqld 09:49:05 PM 1000 - 31484 1.79 2.29 0.00 4.09 2 |__mysqld ... ``` and find which mysql internal threads ``` root@yejr.run [performance_schema]>select thread_id, name ,type from threads where THREAD_OS_ID in (31481, 31482, 31483, 31484); +-----------+---------------------------------------------+------------+ | thread_id | name | type | +-----------+---------------------------------------------+------------+ | 13 | thread/innodb/page_flush_coordinator_thread | BACKGROUND | | 14 | thread/innodb/page_flush_thread | BACKGROUND | | 15 | thread/innodb/page_flush_thread | BACKGROUND | | 16 | thread/innodb/page_flush_thread | BACKGROUND | +-----------+---------------------------------------------+------------+ ```
[7 Sep 2020 13:58]
Ye Jinrong
but it is an empty running instance, and there are no write or update, and no dirty pages to be flushed ``` ... Buffer pool size 524288 Free buffers 506946 Database pages 17336 Old database pages 6253 Modified db pages 0 Pending reads 0 ... ``` and some variables about page cleaner ``` | innodb_page_cleaners | 4 | | innodb_adaptive_flushing | ON | | innodb_adaptive_flushing_lwm | 10 | | innodb_flush_log_at_timeout | 1 | | innodb_flush_log_at_trx_commit | 1 | | innodb_flush_method | fsync | | innodb_flush_neighbors | 0 | | innodb_flush_sync | ON | | innodb_flushing_avg_loops | 30 | ```
[8 Sep 2020 6:55]
Ye Jinrong
I am very sorry, this may be caused by an abnormality in the host of the cloud server, now it back to normal, do i need to close this bug?
[8 Sep 2020 7:48]
MySQL Verification Team
Hi, I'm still analyzing it. Will let you know later today. all best Bogdan
[8 Sep 2020 8:53]
MySQL Verification Team
Hi, Closed as not a bug as this does look like vm abnormality. Let us know if this can be observed again, especially if you can look at the host stats too. thanks Bogdan