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

Server Status Innodb_row_lock_time% is reported in seconds

    XMLWordPrintable

    Details

      Description

      I detected that recent MariaDB versions report the InnoDB_row_lock_time% now in seconds instead of milliseconds.

      This is a bug that destroys all monitoring tools and thus should be fixed immediately.

      It also happens in 10.7.1. Other releases were not tested.

      SQL> start transaction;
      SQL> update test set data = 'lock' where id = 1001;
      -- Wait some seconds and do the same trx in a second console
      SQL> commit;
       
      SQL> show global status like 'innodb_row_lock%';
      +-------------------------------+-------+
      | Variable_name                 | Value |
      +-------------------------------+-------+
      | Innodb_row_lock_current_waits | 0     |
      | Innodb_row_lock_time          | 5     |
      | Innodb_row_lock_time_avg      | 5     |
      | Innodb_row_lock_time_max      | 5     |
      | Innodb_row_lock_waits         | 1     |
      +-------------------------------+-------+
      

      Source: https://mariadb.com/kb/en/innodb-status-variables/#innodb_row_lock_time
      "Total time in milliseconds spent getting InnoDB row locks. "

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              vlad.lesin Vladislav Lesin
              Reporter:
              oli Oli Sennhauser
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:

                  Git Integration

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