Details
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.
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
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- {noformat} Regrettably no full stack is available: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)} Core was generated by `/test/ 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- {noformat} Regrettably no full stack is available: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)} Core was generated by `/test/ 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} |
Assignee | Sergey Vojtovich [ svoj ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Assignee | Sergey Vojtovich [ svoj ] | Sergei Golubchik [ serg ] |
Status | In Progress [ 3 ] | In Review [ 10002 ] |
Link | This issue relates to MDEV-34860 [ MDEV-34860 ] |
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- {noformat} Regrettably no full stack is available: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)} Core was generated by `/test/ 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- {noformat} Regrettably no full stack is available: {noformat:title=11.4.0 57618265ad914824ce78108729829df13c75e224 (Optimized)} Core was generated by `/test/ 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} |
Priority | Minor [ 4 ] | Major [ 3 ] |
Affects Version/s | 11.8 [ 29921 ] |
Status | In Review [ 10002 ] | In Testing [ 10301 ] |
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 ] |
Component/s | Server [ 13907 ] | |
Component/s | Performance Schema [ 15627 ] |
Note that this issue is not PFS specific.