[MDEV-32553] "innodb_monitor_disable = default" does not reset all monitors "enable" stataus to default - Jira

Type: Bug
Status: Open (View Workflow)
Priority: Minor
Resolution: Unresolved
Affects Version/s: 10.4(EOL), 10.5, 10.6, 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL), 11.3(EOL)
Fix Version/s: 10.4(EOL)
Component/s: Storage Engine - InnoDB
Labels:
None

SET GLOBAL innodb_monitor_disable = default;

Does not restore all metrics enabling to default values.
The following test shows differences:

--source include/have_innodb.inc

--source include/have_debug.inc

SET GLOBAL innodb_monitor_disable = default;

--eval select name, enabled from information_schema.innodb_metrics into outfile '$MYSQL_TMP_DIR/out-1'

SET GLOBAL innodb_monitor_disable=all;

SET GLOBAL innodb_monitor_disable = default;

--eval select name, enabled from information_schema.innodb_metrics into outfile '$MYSQL_TMP_DIR/out-2'

--exec diff -u $MYSQL_TMP_DIR/out-1 $MYSQL_TMP_DIR/out-2

--remove-file $MYSQL_TMP_DIR/out-1

--remove-file $MYSQL_TMP_DIR/out-2

is caused by

MDEV-30658 lock_row_lock_current_waits counter in information_schema.innodb_metrics may become negative

is duplicated by

MDEV-32554 mon_lock_wait_current_count test causes innodb.monitor failure

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

MariaDB Server