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

Excessive logging "Cannot close file ./test/FTS_xxx.ibd because of n pending operations and pending fsync

    XMLWordPrintable

Details

    Description

      Within ~1 min test on current 10.6 with default log_warnings level I'm getting in the error log ~8500 records like this:

      2021-03-22  2:58:35 8 [Note] InnoDB: Cannot close file ./test/FTS_00000000000012c8_00000000000015f9_INDEX_1.ibd because of 0 pending operations and pending fsync
      		 
      2021-03-22  2:58:35 8 [Note] InnoDB: Cannot close file ./test/FTS_00000000000012c8_00000000000015f9_INDEX_2.ibd because of 0 pending operations and pending fsync
      		 
      2021-03-22  2:58:35 8 [Note] InnoDB: Cannot close file ./test/FTS_00000000000012c8_00000000000015f9_INDEX_4.ibd because of 0 pending operations and pending fsync
      		 
      2021-03-22  2:58:35 8 [Note] InnoDB: Cannot close file ./test/FTS_00000000000012c8_00000000000015f9_INDEX_5.ibd because of 1 pending operations and pending fsync
      		 
      2021-03-22  2:58:35 8 [Note] InnoDB: Cannot close file ./test/FTS_00000000000012c8_00000000000015f9_INDEX_6.ibd because of 0 pending operations and pending fsync
      		 
      ...

      10.5 seems to produce only those with "0 pending operations", so there are less of them, but still, ~4000 in a few-minute test. And these ones (with zero) are especially confusing.

      I think if these are real problems which a user needs to take care of, there should be warnings or errors (and given the persistence, maybe we are missing at least a debug assertion or something); and if these are just technical notifications, there shouldn't be so many of them.

      Attachments

        1. cannotclosefile.JPG
          cannotclosefile.JPG
          83 kB
        2. mycnf.txt
          2 kB
        3. mysql-0-20211028.log
          219 kB
        4. screenshot-1.png
          screenshot-1.png
          19 kB
        5. screenshot-2.png
          screenshot-2.png
          35 kB

        Issue Links

          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23855 InnoDB log checkpointing causes regression for write-heavy OLTP

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-26381 InnoDB: Failing assertion: fsize != os_offset_t(-1) on CREATE TABLE with many partitions / ENOMEM (out of kernel memory) from fstat handling

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-28110 FLUSH TABLE ... WITH READ LOCK output excessively verbose

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30829 InnoDB: Cannot close file <tablename>.ibd because of pending fsync

          • Major - Major loss of function.
          • Closed

          Activity

            People

              marko Marko Mäkelä
              elenst Elena Stepanova
              Votes:
              4 Vote for this issue
              Watchers:
              11 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.