[MDEV-33285] Assertion `m_table' failed in ha_perfschema::rnd_end on CHECKSUM TABLE - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 11.4, 11.8
Fix Version/s: 10.5.28, 10.6.21, 10.11.11, 11.4.5, 11.7.2
Component/s: Server
Labels:
- sporadic

Description

SET @@max_statement_time=0.0001;

CHECKSUM TABLE performance_schema.rwlock_instances;

CHECKSUM TABLE performance_schema.table_io_waits_summary_by_table;

CHECKSUM TABLE performance_schema.users;

CHECKSUM TABLE performance_schema.cond_instances;

Leads to:

11.4.0 57618265ad914824ce78108729829df13c75e224
mariadbd: /test/bb-11.4-MDEV-7850_opt/storage/perfschema/ha_perfschema.cc:341: virtual int ha_perfschema::rnd_end(): Assertion `m_table' failed.

Regrettably no full stack is available:

11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)
Core was generated by `/test/MDEV-7850_MD161223-mariadb-11.4.0-linux-x86_64-opt/bin/mariadbd --no-defa'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3)
at ./nptl/pthread_mutex_lock.c:577
[Current thread is 1 (LWP 3490259)]
(gdb) bt
#0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3) at ./nptl/pthread_mutex_lock.c:577
#1 0x0000000000000000 in ?? ()

However an earlier run captured the following frames:

11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)
#1 ha_perfschema::rnd_end
#2 ha_perfschema::rnd_end
#3 handler::ha_rnd_end
#4 mysql_checksum_table

Attachments

Issue Links

relates to

MDEV-34860 Implement MAX_EXECUTION_TIME hint

Stalled

Activity

Ascending order - Click to sort in descending order

Roel Van de Paar created issue - 2024-01-20 00:16

Roel Van de Paar made changes - 2024-01-20 00:18

Field	Original Value	New Value
Description	Non-important issue at all, just logging so it can be added to filters. Extremely sporadic. Expect run times of 1h+ even with 200 threads repeating the SQL. Only one of the CHECKSUM TABLE statements is required, they can all fail with the said assertion. {code:sql} SET @@max_statement_time=0.0001; CHECKSUM TABLE performance_schema.rwlock_instances; CHECKSUM TABLE performance_schema.table_io_waits_summary_by_table; CHECKSUM TABLE performance_schema.users; {code} Leads to: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224} mariadbd: /test/bb-11.4-~~MDEV-7850~~_opt/storage/perfschema/ha_perfschema.cc:341: virtual int ha_perfschema::rnd_end(): Assertion `m_table' failed. {noformat} Regrettably no full stack is available: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)} Core was generated by `/test/~~MDEV-7850~~_MD161223-mariadb-11.4.0-linux-x86_64-opt/bin/mariadbd --no-defa'. Program terminated with signal SIGABRT, Aborted. #0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3) at ./nptl/pthread_mutex_lock.c:577 [Current thread is 1 (LWP 3490259)] (gdb) bt #0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3) at ./nptl/pthread_mutex_lock.c:577 #1 0x0000000000000000 in ?? () {noformat} However an earlier run captured the following frames: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)} #1 ha_perfschema::rnd_end #2 ha_perfschema::rnd_end #3 handler::ha_rnd_end #4 mysql_checksum_table {noformat}	Non-important issue at all, just logging so it can be added to filters. Extremely sporadic. Expect run times of 1h+ even with 200 threads repeating the SQL. Only one of the CHECKSUM TABLE statements is required, they can all fail with the given assertion. {code:sql} SET @@max_statement_time=0.0001; CHECKSUM TABLE performance_schema.rwlock_instances; CHECKSUM TABLE performance_schema.table_io_waits_summary_by_table; CHECKSUM TABLE performance_schema.users; {code} Leads to: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224} mariadbd: /test/bb-11.4-~~MDEV-7850~~_opt/storage/perfschema/ha_perfschema.cc:341: virtual int ha_perfschema::rnd_end(): Assertion `m_table' failed. {noformat} Regrettably no full stack is available: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)} Core was generated by `/test/~~MDEV-7850~~_MD161223-mariadb-11.4.0-linux-x86_64-opt/bin/mariadbd --no-defa'. Program terminated with signal SIGABRT, Aborted. #0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3) at ./nptl/pthread_mutex_lock.c:577 [Current thread is 1 (LWP 3490259)] (gdb) bt #0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3) at ./nptl/pthread_mutex_lock.c:577 #1 0x0000000000000000 in ?? () {noformat} However an earlier run captured the following frames: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)} #1 ha_perfschema::rnd_end #2 ha_perfschema::rnd_end #3 handler::ha_rnd_end #4 mysql_checksum_table {noformat}

Sergey Vojtovich made changes - 2024-11-08 15:15

Assignee

Sergey Vojtovich [ svoj ]

Sergey Vojtovich made changes - 2024-11-08 15:15

Status

Open [ 1 ]

In Progress [ 3 ]

Sergey Vojtovich made changes - 2024-11-08 15:16

Assignee	Sergey Vojtovich [ svoj ]	Sergei Golubchik [ serg ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Roel Van de Paar made changes - 2025-01-15 03:54

Link

This issue relates to MDEV-34860 [ MDEV-34860 ]

Roel Van de Paar made changes - 2025-01-15 03:59

Description

Non-important issue at all, just logging so it can be added to filters. Extremely sporadic. Expect run times of 1h+ even with 200 threads repeating the SQL. Only one of the CHECKSUM TABLE statements is required, they can all fail with the given assertion.
{code:sql}
SET @@max_statement_time=0.0001;
CHECKSUM TABLE performance_schema.rwlock_instances;
CHECKSUM TABLE performance_schema.table_io_waits_summary_by_table;
CHECKSUM TABLE performance_schema.users;
{code}
Leads to:
{noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224}
mariadbd: /test/bb-11.4-~~MDEV-7850~~_opt/storage/perfschema/ha_perfschema.cc:341: virtual int ha_perfschema::rnd_end(): Assertion `m_table' failed.
{noformat}
Regrettably no full stack is available:
{noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)}
Core was generated by `/test/~~MDEV-7850~~_MD161223-mariadb-11.4.0-linux-x86_64-opt/bin/mariadbd --no-defa'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3)
at ./nptl/pthread_mutex_lock.c:577
[Current thread is 1 (LWP 3490259)]
(gdb) bt
#0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3) at ./nptl/pthread_mutex_lock.c:577
#1 0x0000000000000000 in ?? ()
{noformat}
However an earlier run captured the following frames:
{noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)}
#1 ha_perfschema::rnd_end
#2 ha_perfschema::rnd_end
#3 handler::ha_rnd_end
#4 mysql_checksum_table
{noformat}

Non-important issue at all, just logging so it can be added to filters. Extremely sporadic. Expect run times of 1h+ even with 200 threads repeating the SQL. Only one of the CHECKSUM TABLE statements is required, they can all fail with the given assertion.
{code:sql}
SET @@max_statement_time=0.0001;
CHECKSUM TABLE performance_schema.rwlock_instances;
CHECKSUM TABLE performance_schema.table_io_waits_summary_by_table;
CHECKSUM TABLE performance_schema.users;
CHECKSUM TABLE performance_schema.cond_instances;
{code}
Leads to:
{noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224}
mariadbd: /test/bb-11.4-~~MDEV-7850~~_opt/storage/perfschema/ha_perfschema.cc:341: virtual int ha_perfschema::rnd_end(): Assertion `m_table' failed.
{noformat}
Regrettably no full stack is available:
{noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)}
Core was generated by `/test/~~MDEV-7850~~_MD161223-mariadb-11.4.0-linux-x86_64-opt/bin/mariadbd --no-defa'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3)
at ./nptl/pthread_mutex_lock.c:577
[Current thread is 1 (LWP 3490259)]
(gdb) bt
#0 0x00001529ba6969fc in __pthread_mutex_lock_full (mutex=0x3541d3) at ./nptl/pthread_mutex_lock.c:577
#1 0x0000000000000000 in ?? ()
{noformat}
However an earlier run captured the following frames:
{noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)}
#1 ha_perfschema::rnd_end
#2 ha_perfschema::rnd_end
#3 handler::ha_rnd_end
#4 mysql_checksum_table
{noformat}

Roel Van de Paar made changes - 2025-01-15 03:59

Priority

Minor [ 4 ]

Major [ 3 ]

Roel Van de Paar made changes - 2025-01-15 03:59

Affects Version/s

11.8 [ 29921 ]

Sergei Golubchik made changes - 2025-01-22 14:04

Status

In Review [ 10002 ]

In Testing [ 10301 ]

Sergei Golubchik made changes - 2025-01-22 14:32

Fix Version/s		10.5.28 [ 29952 ]
Fix Version/s		10.6.21 [ 29953 ]
Fix Version/s		10.11.11 [ 29954 ]
Fix Version/s		11.4.5 [ 29956 ]
Fix Version/s		11.7.2 [ 29914 ]
Fix Version/s	11.4 [ 29301 ]
Assignee	Sergei Golubchik [ serg ]	Sergey Vojtovich [ svoj ]
Resolution		Fixed [ 1 ]
Status	In Testing [ 10301 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2025-01-22 14:33

Component/s		Server [ 13907 ]
Component/s	Performance Schema [ 15627 ]

People

Assignee:: Sergey Vojtovich

Reporter:: Roel Van de Paar

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2024-01-20 00:16

Updated:: 2025-01-28 18:31

Resolved:: 2025-01-22 14:32

Git Integration

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

MariaDB Server

Details

Description

Attachments

Issue Links

Activity

People

Dates

Git Integration