Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.2.16
-
10.2.16-MariaDB-10.2.16+maria~trusty-log
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
Description
Galera Cluster node crashes while adding new partitions to the table with more than 250 partitions. We have scheduled event which is running procedure for automatically adding new partitions.
Problem is experienced on Mariadb Galera Cluster 10.0.34 and 10.2.16 versions.
We have three more tables with more than 150 partitions and same procedure for adding new partitions and everything works without any problems.
Trace:
2018-11-25 18:00:52 139643177436928 [Warning] Sort aborted, host: 10.4.0.8, user: my_user, thread: 166381, query: select missioneve0_.id as id2_23_, missioneve0_.channel as channel3_23_, missioneve0_.created_at as created_4_23_, missioneve0_.event_type as event_ty5_23_, missioneve0_.extra_data as extra_da6_23_, missioneve0_.id_message as id_messa7_23_, missioneve0_.tracking_id as tracking8_23_, missioneve0_.id_user as id_user9_23_, missioneve0_.id_mission as id_miss10_23_, missioneve0_.uuid_user as uuid_us11_23_, missioneve0_.discriminator as discrimi1_23_ from touchpoint_event_log missioneve0_ left outer join missions missionent1_ on missioneve0_.id_mission=missionent1_.id where missioneve0_.discriminator in (2, 3) and missioneve0_.event_type='testMission' and missionent1_.id=137734 and missioneve0_.created_at>'2018-10-25 18:00:52' order by missioneve0_.created_at desc
pure virtual method called
terminate called without an active exception
181125 18:00:52 [ERROR] mysqld got signal 6 ;
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.2.16-MariaDB-10.2.16+maria~trusty-log
key_buffer_size=16777216
read_buffer_size=2097152
max_used_connections=91
max_threads=8002
thread_count=150
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 17599632 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f00b8000a88
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 = 0x7f0135fc7e70 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55f9b92e050e]
/usr/sbin/mysqld(handle_fatal_signal+0x355)[0x55f9b8d6c175]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f0e70c7f330]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f0e702d2c37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f0e702d6028]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(ZN9gnu_cxx27_verbose_terminate_handlerEv+0x155)[0x7f0e709cb535]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e6d6)[0x7f0e709c96d6]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5e703)[0x7f0e709c9703]
/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0x5f1bf)[0x7f0e709ca1bf]
/usr/sbin/mysqld(_ZN7handler16ha_external_lockEP3THDi+0xc3)[0x55f9b8d75e63]
/usr/sbin/mysqld(+0x75c5ab)[0x55f9b8e565ab]
/usr/sbin/mysqld(_Z24mysql_unlock_read_tablesP3THDP13st_mysql_lock+0x68)[0x55f9b8e56df8]
/usr/sbin/mysqld(_ZN4JOIN9join_freeEv+0x16b)[0x55f9b8c190bb]
/usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0x9b5)[0x55f9b8c2e2b5]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x33)[0x55f9b8c2e553]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x11a)[0x55f9b8c2e6aa]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x24c)[0x55f9b8c2f1fc]
/usr/sbin/mysqld(+0x419f0a)[0x55f9b8b13f0a]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2aa4)[0x55f9b8bdc6e4]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x2bd)[0x55f9b8be2fad]
/usr/sbin/mysqld(+0x4e987f)[0x55f9b8be387f]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1aef)[0x55f9b8be59ff]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x165)[0x55f9b8be6b65]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1aa)[0x55f9b8ca9bfa]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x55f9b8ca9d1d]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7f0e70c77184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f0e70399ffd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f00b800f230): is an invalid pointer
Connection ID (thread ID): 166381
Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
We think the query pointer is invalid, but we will try to print it anyway.
Query: select missioneve0_.id as id2_23_, missioneve0_.channel as channel3_23_, missioneve0_.created_at as created_4_23_, missioneve0_.event_type as event_ty5_23_, missioneve0_.extra_data as extra_da6_23_, missioneve0_.id_message as id_messa7_23_, missioneve0_.tracking_id as tracking8_23_, missioneve0_.id_user as id_user9_23_, missioneve0_.id_mission as id_miss10_23_, missioneve0_.uuid_user as uuid_us11_23_, missioneve0_.discriminator as discrimi1_23_ from touchpoint_event_log missioneve0_ left outer join missions missionent1_ on missioneve0_.id_mission=missionent1_.id where missioneve0_.discriminator in (2, 3) and missioneve0_.event_type='testMission' and missionent1_.id=137734 and missioneve0_.created_at>'2018-10-25 18:00:52' order by missioneve0_.created_at desc
Attachments
Issue Links
- relates to
-
MDEV-17839 Crash (pure virtual method called) in or around handler::ha_external_lock for simple SELECT with join
- Closed