Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. 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.)

Details

    Description

      Hi,
      I migrated from MySQL 5.6.36 to MariaDB 10.2.8 32bit on Windows 2008 R1.
      I have started to see the following in our production environment.

      2017-08-29 10:45:24 4432 [Note] InnoDB: page_cleaner: 1000ms intended loop took 4197ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)

      I have not made any changes to the configuration file (my.ini); I was wondering do I need to

      the settings are:-

      MariaDB [(none)]> show global variables like 'innodb_buffer%';
      		 
      +-------------------------------------+----------------+
      		 
      | Variable_name                       | Value          |
      		 
      +-------------------------------------+----------------+
      		 
      | innodb_buffer_pool_chunk_size       | 134217728      |
      		 
      | innodb_buffer_pool_dump_at_shutdown | ON             |
      		 
      | innodb_buffer_pool_dump_now         | OFF            |
      		 
      | innodb_buffer_pool_dump_pct         | 25             |
      		 
      | innodb_buffer_pool_filename         | ib_buffer_pool |
      		 
      | innodb_buffer_pool_instances        | 1              |
      		 
      | innodb_buffer_pool_load_abort       | OFF            |
      		 
      | innodb_buffer_pool_load_at_startup  | ON             |
      		 
      | innodb_buffer_pool_load_now         | OFF            |
      		 
      | innodb_buffer_pool_populate         | OFF            |
      		 
      | innodb_buffer_pool_size             | 268435456      |
      		 
      +-------------------------------------+----------------+
      		 
      11 rows in set (0.00 sec)

      Do I need to increase innodb_buffer_pool_instances, or anything else to stop this latency which I never saw logged with MySQL 5.6.36?

      many thanks for your advice and guidance.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13949 Improve help when reporting page cleaner loop taking too long

          • Major - Major loss of function.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-16526 Overhaul the InnoDB page flushing

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23399 10.5 performance regression with IO-bound tpcc

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14550 Error log flood : "InnoDB: page_cleaner: 1000ms intended loop took N ms. The settings might not be optimal."

          • Major - Major loss of function.
          • Closed
          links to

          Web Link Bug #71662 InnoDB background threads should be configurable to reduce power consumption

          Web Link Bug #75846 page_cleaner thread configuration warning spams error log on laptops

          Web Link Bug #76661 Improve help when reporting page cleaner loop taking too long

          Activity

            Transition Time In Source Status Execution Times
            Elena Stepanova made transition -
            Open Confirmed
            		21d 1h 10m 1
            Marko Mäkelä made transition -
            Confirmed Closed
            		273d 4h 1

            People

              marko Marko Mäkelä
              slaterss Stuart Slater
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.