MySQL Log Messages: page_cleaner: 1000ms intended loop took 8120ms.

2024-05-23 22:34:13

MySQL Log Messages: page_cleaner: 1000ms intended loop took 8120ms. The settings might not be optimal. (flushed=0 and evicted=25273, during the time.) (Doc ID 2014477.1)

正在上传…重新上传取消To Bottom

In this Document

Goal

Solution

References

APPLIES TO:

MySQL Server - Version 5.7 and later
Information in this document applies to any platform.

GOAL

Guidance for configuring the server when seeing these messages frequently:

[Note] InnoDB: page_cleaner: 1000ms intended loop took 4120ms. The settings might not be optimal. (flushed=0 and evicted=85273, during the time.)
[Note] InnoDB: page_cleaner: 1000ms intended loop took 5280ms. The settings might not be optimal. (flushed=0 and evicted=117010, during the time.)
[Note] InnoDB: page_cleaner: 1000ms intended loop took 5338ms. The settings might not be optimal. (flushed=0 and evicted=135394, during the time.)
[Note] InnoDB: page_cleaner: 1000ms intended loop took 18890ms. The settings might not be optimal. (flushed=0 and evicted=18927, during the time.)
[Note] InnoDB: page_cleaner: 1000ms intended loop took 6591ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)

SOLUTION

The note means that page cleaner took longer than it should. Either not enough page cleaner threads are configured, or each thread is having too much work to do to complete within 1000ms.

One should review KM 1531329.1 in addition to this.

Check the following items to start your investigation:

innodb_buffer_pool_size It is large enough to maintain hot data in memory?
innodb_buffer_pool_instances Split large buffer pools to avoid mutex contention on servers with many CPUs.
innodb_page_cleaners. Avoid setting this less than 4.
Allow the OS to set higher priority for the page clean thread. See instructions here.
innodb_lru_scan_depth
Determine physical disk i/o capabilities, and set appropriate innodb_io_capacity

The old default of 1 page cleaner thread is not enough for large systems.

Aim to make number of page cleaners equal to the lesser of number of buffer pool instances or number of CPU cores.

To aid helping to monitor the page cleaner flushing activity, the innodb_metrics table has some counters that can be monitored over time:

mysql> set global innodb_monitor_disable=all;
Query OK, 0 rows affected (0.39 sec)

mysql> set global innodb_monitor_reset_all=all;
Query OK, 0 rows affected (0.08 sec)

mysql> set global innodb_monitor_enable=all;
Query OK, 0 rows affected (0.06 sec)

mysql> do sleep(10);
Query OK, 0 rows affected (9.20 sec)

mysql> select name,count,type,comment from information_schema.innodb_metrics where name like 'buffer_flush%';
+-------------------------------------+--------+------------+----------------------------------------------------------------+
| name                                | count | type       | comment                                                        |
+-------------------------------------+--------+------------+----------------------------------------------------------------+
| buffer_flush_batch_scanned          |     42 | set_owner | Total pages scanned as part of flush batch                     |
| buffer_flush_batch_num_scan         |     10 | set_member | Number of times buffer flush list flush is called              |
| buffer_flush_batch_scanned_per_call |      1 | set_member | Pages scanned per flush batch scan                             |
| buffer_flush_batch_rescan           |      1 | counter    | Number of times rescan of flush list forced                    |
| buffer_flush_batch_total_pages      |    110 | set_owner | Total pages flushed as part of flush batch                     |
| buffer_flush_batches                |     10 | set_member | Number of flush batches                                        |
| buffer_flush_batch_pages            |      1 | set_member | Pages queued as a flush batch                                  |
| buffer_flush_neighbor_total_pages   |     83 | set_owner | Total neighbors flushed as part of neighbor flush              |
| buffer_flush_neighbor               |     27 | set_member | Number of times neighbors flushing is invoked                  |
| buffer_flush_neighbor_pages         |      0 | set_member | Pages queued as a neighbor batch                               |
| buffer_flush_n_to_flush_requested   |     71 | counter    | Number of pages requested for flushing.                        |
| buffer_flush_avg_page_rate          |     18 | counter    | Average number of pages at which flushing is happening         |
| buffer_flush_lsn_avg_rate           | 260304 | counter    | Average redo generation rate                                   |
| buffer_flush_pct_for_dirty          |      0 | counter    | Percent of IO capacity used to avoid max dirty page limit      |
| buffer_flush_pct_for_lsn            |     62 | counter    | Percent of IO capacity used to avoid reusable redo space limit |
| buffer_flush_sync_waits             |      0 | counter    | Number of times a wait happens due to sync flushing            |
| buffer_flush_adaptive_total_pages   |    110 | set_owner | Total pages flushed as part of adaptive flushing               |
| buffer_flush_adaptive               |     10 | set_member | Number of adaptive batches                                     |
| buffer_flush_adaptive_pages         |      1 | set_member | Pages queued as an adaptive batch                              |
| buffer_flush_sync_total_pages       |      0 | set_owner | Total pages flushed as part of sync batches                    |
| buffer_flush_sync                   |      0 | set_member | Number of sync batches                                         |
| buffer_flush_sync_pages             |      0 | set_member | Pages queued as a sync batch                                   |
| buffer_flush_background_total_pages |      0 | set_owner | Total pages flushed as part of background batches              |
| buffer_flush_background             |      0 | set_member | Number of background batches                                   |
| buffer_flush_background_pages       |      0 | set_member | Pages queued as a background batch                             |
+-------------------------------------+--------+------------+----------------------------------------------------------------+
25 rows in set (0.06 sec)

REFERENCES

MySQL :: MySQL 8.0 Reference Manual :: 15.14 InnoDB Startup Options and System Variables
NOTE:1531329.1 - Recommended Settings for MySQL 5.6, 5.7, 8.0 Server for Online Transaction Processing (OLTP) and Benchmarking

MySQL Log Messages: page_cleaner: 1000ms intended loop took 8120ms.相关推荐

从库延迟增大，MySQL日志出现InnoDB: page_cleaner: 1000ms intended loop took 17915ms.
InnoDB: page_cleaner: 1000ms intended loop took 17915ms. 查看服务器top,发现CPU出现大量wait占用同时,用iostat查看也发现uti ...
InnoDB：page_cleaner：1000ms intended loop 解决
1.在查看mysqllog日志的时候不经意间发现一条这个提示: 2022-12-22T05:42:24.581836Z 119 [Note] Aborted connection 119 to db ...
InnoDB：page_cleaner：1000ms intended loop took [xxx]ms解决
1.在查看mysqllog日志的时候不经意间发现一条这个提示: 1 [Note] InnoDB: page_cleaner: 1000ms intended loop took 16111ms. Th ...
linuxmessage日志消失_某工的centos7 启动了rsyslog之后，日志/var/log/messages等都不产生日志了，都是空的。求大神解决！...
之前一直有日志生成的,正常运行,自从前几天搞了下好像重启了下rsyslog ,最后一次轮替日志之后,/var/log/message, /var/log/secure等都不记录了,并且都是空文件. 求 ...
（转载）把syslog接收的远程日志从/var/log/messages中分开
今天突然要配置Linux的syslog服务器,摸了一早上才弄好.记录远程机器发来的syslog消息倒是容易(网上到处都是),不过按照默认的设置,syslog会将所有信息都给写入 /var/log/me ...
php mysql log文件,mysql log文件【读书笔记1】_MySQL
bitsCN.com mysql log文件[读书笔记1] 一,错误日志文件:Error.log 记录Mysql Server运行过程所有较为严重的警告或错误信息,以及Mysql Server启动和关 ...
分析 linux /var/log/messages,2009-11-30 15:30 Linux系统日志/var/log/messages （转）
日志文件其实是纯文本的文件,每一行就是一个消息.只要是在Linux下能够处理纯文本的工具都能用来查看日志文件.日志文件总是很大的,因为从你第一次启动Linux开始,消息就都累积在日志文件中.看日志文件 ...
linux中boot.log,messages,secure,dnf,cron日志文件的作用
/var/log/boot.log 与系统启动相关的信息的仓库 /var/log/syslog 或/var/log/messages 包含系统相关信息,几乎包含所有活动数据的信息,基于redhat的l ...
解决无/var/log/messages 问题
转载于:https://blog.csdn.net/C_Major/article/details/51321684 1 内核编程insmod后,Ubuntu查看日志无/var/log/message ...

最新文章

热门文章