Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.16
-
10.2.2-4, 10.1.18
Description
MariaDB 10.1.16 server crashed after running for 1 hour with the query_cache_info plugin enabled:
INSTALL PLUGIN query_cache_info SONAME 'query_cache_info';
|
with the following related settings:
mysql ((none))> show global variables like 'query%';
|
+------------------------------+----------+
|
| Variable_name | Value |
|
+------------------------------+----------+
|
| query_alloc_block_size | 16384 |
|
| query_cache_limit | 8388608 |
|
| query_cache_min_res_unit | 1024 |
|
| query_cache_size | 67108864 |
|
| query_cache_strip_comments | OFF |
|
| query_cache_type | ON |
|
| query_cache_wlock_invalidate | OFF |
|
| query_prealloc_size | 24576 |
|
+------------------------------+----------+
|
and query cache related status typically looking like this:
| Qcache_free_blocks | 432 |
|
| Qcache_free_memory | 14381680 |
|
| Qcache_hits | 1320200 |
|
| Qcache_inserts | 1980307 |
|
| Qcache_lowmem_prunes | 252808 |
|
| Qcache_not_cached | 1089705 |
|
| Qcache_queries_in_cache | 17940 |
|
| Qcache_total_blocks | 37205 |
|
|
Stack trace is the following:
160909 10:36:35 [ERROR] mysqld got signal 11 ;
|
This could be because you hit a bug. It is also possible that this binary
|
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
|
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
|
|
|
We will try our best to scrape up some info that will hopefully help
|
diagnose the problem, but since we have already crashed,
|
something is definitely wrong and this may fail.
|
|
|
Server version: 10.1.16-MariaDB
|
key_buffer_size=67108864
|
read_buffer_size=1048576
|
max_used_connections=61
|
max_threads=1002
|
thread_count=60
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3164184 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x0x7f5ec28ba008
|
Attempting backtrace. You can use the following information to find out
|
where mysqld died. If you see no messages after this, something went
|
terribly wrong...
|
stack_bottom = 0x7f6bd4dad288 thread_stack 0x48400
|
/opt/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0xc099ee]
|
/opt/mysql/bin/mysqld(handle_fatal_signal+0x4ba)[0x7664da]
|
/lib64/libpthread.so.0(+0xf100)[0x7f6be9f89100]
|
/opt/mysql/lib/plugin/query_cache_info.so(+0xf35)[0x7f6bde5fef35]
|
/opt/mysql/bin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x2ee)[0x612dfe]
|
/opt/mysql/bin/mysqld(_ZN4JOIN10exec_innerEv+0x907)[0x609927]
|
/opt/mysql/bin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x28f)[0x60855f]
|
/opt/mysql/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x250)[0x60c130]
|
/opt/mysql/bin/mysqld[0x5ac8e8]
|
/opt/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x14f7)[0x5b2a97]
|
/opt/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x2b4)[0x5baeb4]
|
/opt/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x23a7)[0x5bdee7]
|
/opt/mysql/bin/mysqld(_Z10do_commandP3THD+0x2a7)[0x5be2f7]
|
/opt/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x183)[0x68d423]
|
/opt/mysql/bin/mysqld(handle_one_connection+0x42)[0x68d642]
|
/lib64/libpthread.so.0(+0x7dc5)[0x7f6be9f81dc5]
|
/lib64/libc.so.6(clone+0x6d)[0x7f6be8e5fced]
|
and crashing query was:
select statement_schema, statement_text, result_blocks_count, result_blocks_size from information_schema.query_cache_info
|