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

The status variable Innodb_buffer_pool_read_requests is not updated correctly

Details

    Description

      In MDEV-26827, some monitoring was changed.
      Some status variables were changed to point directly to the underlying variables, like this:

        {"buffer_pool_read_requests", &buf_pool.stat.n_page_gets, SHOW_SIZE_T},
      

      Unlike all other variables in buf_pool.stat this particular one is divided into shards for performance reasons (MDEV-21212). So, the status variable would only reflect the contents of the first shard and not the entire counter. Thanks to dragle for noticing this.

      Note: This counter is inaccurate by design. If we protected it correctly, it would introduce a performance bottleneck.

      Attachments

        Issue Links

          Activity

            marko Marko Mäkelä created issue -
            marko Marko Mäkelä made changes -
            Field Original Value New Value
            marko Marko Mäkelä made changes -
            issue.field.resolutiondate 2023-05-19 13:18:03.0 2023-05-19 13:18:03.65
            marko Marko Mäkelä made changes -
            Fix Version/s 10.6.14 [ 28914 ]
            Fix Version/s 10.9.7 [ 28916 ]
            Fix Version/s 10.10.5 [ 28917 ]
            Fix Version/s 10.11.4 [ 28918 ]
            Fix Version/s 11.0.3 [ 28920 ]
            Fix Version/s 11.1.2 [ 28921 ]
            Fix Version/s 10.6 [ 24028 ]
            Fix Version/s 10.9 [ 26905 ]
            Fix Version/s 10.10 [ 27530 ]
            Fix Version/s 10.11 [ 27614 ]
            Fix Version/s 11.0 [ 28320 ]
            Fix Version/s 11.1 [ 28549 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            dragle Daniel Ragle added a comment -

            Thanks, I believe this is taken care of in the 10.6.14 build you pointed me to in a separate thread. Unfortunately the only machine I had that displayed the problem was reverted early this week to 10.6.12, and when I try to load new 10.6.13 instances in VMs they don't display this behavior.

            But not seeing the issue consistently would seem to make sense based on your explanation, and I'm not seeing it in the 10.6.14 build either, so this should be good.

            dragle Daniel Ragle added a comment - Thanks, I believe this is taken care of in the 10.6.14 build you pointed me to in a separate thread. Unfortunately the only machine I had that displayed the problem was reverted early this week to 10.6.12, and when I try to load new 10.6.13 instances in VMs they don't display this behavior. But not seeing the issue consistently would seem to make sense based on your explanation, and I'm not seeing it in the 10.6.14 build either, so this should be good.
            julien.fritsch Julien Fritsch made changes -
            julien.fritsch Julien Fritsch made changes -
            julien.fritsch Julien Fritsch made changes -
            rogerd007 Roger added a comment -

            This bug still appears to exist in 10.9.8.

            MariaDB [(none)]> select count from information_schema.INNODB_METRICS where name = 'buffer_pool_read_requests';
            -------

            count

            -------

            83743

            MariaDB [(none)]> show global status like 'Innodb_buffer_pool_read_requests';
            ---------------------------------------+

            Variable_name Value

            ---------------------------------------+

            Innodb_buffer_pool_read_requests 0

            ---------------------------------------+

            rogerd007 Roger added a comment - This bug still appears to exist in 10.9.8. MariaDB [(none)] > select count from information_schema.INNODB_METRICS where name = 'buffer_pool_read_requests'; ------- count ------- 83743 MariaDB [(none)] > show global status like 'Innodb_buffer_pool_read_requests'; --------------------------------- ------+ Variable_name Value --------------------------------- ------+ Innodb_buffer_pool_read_requests 0 --------------------------------- ------+
            marko Marko Mäkelä made changes -
            danblack Daniel Black added a comment -

            rogerd007 note the 10.9 series (and 10.10) are out of maintaince as they where short term support only.

            For maintaince policy - see https://mariadb.org/about/#maintenance-policy

            danblack Daniel Black added a comment - rogerd007 note the 10.9 series (and 10.10) are out of maintaince as they where short term support only. For maintaince policy - see https://mariadb.org/about/#maintenance-policy

            People

              marko Marko Mäkelä
              marko Marko Mäkelä
              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.