Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL)
-
None
Description
There are too many messages in form
"InnoDB: page_cleaner: 1000ms intended loop took 4450ms. The settings might not be optimal".
An example of the flood is here https://jira.mariadb.org/secure/attachmentzip/unzip/64627/44712%5B0%5D/
A message like this is written every 15 seconds.
A better idea is to write only seldomly. If this is something performance related, you can expose the average slowness via status variable or something like that.
Attachments
Issue Links
- relates to
-
MDEV-13670 [Note] InnoDB: page_cleaner: 1000ms intended loop took XXXXms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
- Closed
-
MDEV-16526 Overhaul the InnoDB page flushing
- Closed
-
MDEV-23399 10.5 performance regression with IO-bound tpcc
- Closed
-
MDEV-27466 Deadlock when purge thread races the flush thread for page lock under Innodb redo log space pressure
- Closed
-
MDEV-28415 ALTER TABLE on a large table hangs InnoDB
- Closed