Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-14550

Error log flood : "InnoDB: page_cleaner: 1000ms intended loop took N ms. The settings might not be optimal."

Details

    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

          Bug - A problem which impairs or prevents the functions of the product. 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.)

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          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-27466 Deadlock when purge thread races the flush thread for page lock under Innodb redo log space pressure

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28415 ALTER TABLE on a large table hangs InnoDB

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            marko Marko Mäkelä added a comment -

            The message was hidden at the default log_warnings level (2 or less). The actual problem will be addressed in MDEV-16526.

            marko Marko Mäkelä added a comment - The message was hidden at the default log_warnings level (2 or less). The actual problem will be addressed in MDEV-16526 .
            marko Marko Mäkelä added a comment -

            While working on MDEV-23399, I found a likely explanation for these messages. The ‘flush_list flushing’ would actually wait for buffer pool page latches, and therefore a single batch can take an arbitrarily long time.

            marko Marko Mäkelä added a comment - While working on MDEV-23399 , I found a likely explanation for these messages. The ‘flush_list flushing’ would actually wait for buffer pool page latches, and therefore a single batch can take an arbitrarily long time.

            People

              marko Marko Mäkelä
              wlad Vladislav Vaintroub
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.