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

mon_lock_wait_current_count test causes innodb.monitor failure

    XMLWordPrintable

Details

    Description

      The following statement in the test:

      SET GLOBAL innodb_monitor_disable=all;

      causes result changes in innodb.monitor in the following query:

      select name, if(enabled,'enabled','disabled') status                            
      from information_schema.innodb_metrics;

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32553 "innodb_monitor_disable = default" does not reset all monitors "enable" stataus to default

          • Major - Major loss of function.
          • Open
          is caused by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30658 lock_row_lock_current_waits counter in information_schema.innodb_metrics may become negative

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

          Activity

            People

              vlad.lesin Vladislav Lesin
              vlad.lesin Vladislav Lesin
              Votes:
              0 Vote for this issue
              Watchers:
              1 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.