[MDEV-32554] mon_lock_wait_current_count test causes innodb.monitor failure Created: 2023-10-23  Updated: 2023-10-24  Resolved: 2023-10-23

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests
Affects Version/s: 10.6
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Vladislav Lesin Assignee: Vladislav Lesin
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-32553 "innodb_monitor_disable = default" do... Open
Problem/Incident
is caused by MDEV-30658 lock_row_lock_current_waits counter i... Closed

 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;



 Comments   
Comment by Vladislav Lesin [ 2023-10-23 ]

The root case is MDEV-32553.

Comment by Vladislav Lesin [ 2023-10-23 ]

The following commit will be applied in 10.5->10.6 merge as a part of MDEV-30658 conflicts resolution.

Generated at Thu Feb 08 10:32:14 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.