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

Enabling the InnoDB Lock Monitor with the standard InnoDB Plugin enabled does not log output to error log

    XMLWordPrintable

Details

    Description

      If you are running MariaDB 5.5.30 (at least on Windows), you have enabled the "standard InnoDB Plugin" (i.e., not XtraDB+), and you enable the InnoDB Lock Monitor (i.e., CREATE TABLE innodb_lock_monitor (id int) ENGINE=InnoDB), extra lock information is printed when you invoke SHOW ENGINE INNODB STATUS, however, this information is not logged to the Error log at all now.

      1. Start MariaDB 5.5.30 with the standard InnoDB Plugin enabled:

      [mysqld]
      ignore_builtin_innodb
      plugin-load=innodb=ha_innodb.dll;innodb_trx=ha_innodb.dll;innodb_locks=ha_innodb.dll;innodb_lock_waits=ha_innodb.dll;innodb_cmp=ha_innodb.dll;innodb_cmp_reset=ha_innodb.dll;innodb_cmpmem=ha_innodb.dll;innodb_cmpmem_reset=ha_innodb.dll

      2. SHOW ENGINE INNODB STATUS\G
      3. CREATE TABLE innodb_lock_monitor (id int) ENGINE=InnoDB;
      4. SHOW ENGINE INNODB STATUS\G
      5. Compare the 2 SHOW ENGINE INNODB STATUS Outputs. You'll see the extra lock information is correctly in the 2nd output.
      6. Examine the error log. You'll see no SHOW ENGINE INNODB STATUS is logged to the error log.

      Attachments

        Activity

          People

            serg Sergei Golubchik
            ccalender Chris Calender (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.