Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.0.14-galera
-
Fix Version/s: 10.0.16-galera, 10.1.3
-
Component/s: wsrep
-
Labels:
-
Environment:Ubuntu 14.04.1 amd64
MariaDB Galera Cluster 10.0.14
Galera 25.3.5-wheezy
Description
I use sakila database for my test. http://dev.mysql.com/doc/index-other.html (I joinned my files to this Issue)
I run it on non clustured MariaDB and all work greats.
When I run the same Shema creation SQL file on MariaDB Galera, the node crash at the CREATE DEFINER line with this message in syslog;
Nov 26 12:36:22 ubuntuserver1 mysqld: 141126 12:36:22 [ERROR] mysqld got signal 11 ; Nov 26 12:36:22 ubuntuserver1 mysqld: This could be because you hit a bug. It is also possible that this binary Nov 26 12:36:22 ubuntuserver1 mysqld: or one of the libraries it was linked against is corrupt, improperly built, Nov 26 12:36:22 ubuntuserver1 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware. Nov 26 12:36:22 ubuntuserver1 mysqld: Nov 26 12:36:22 ubuntuserver1 mysqld: To report this bug, see http://kb.askmonty.org/en/reporting-bugs Nov 26 12:36:22 ubuntuserver1 mysqld: Nov 26 12:36:22 ubuntuserver1 mysqld: We will try our best to scrape up some info that will hopefully help Nov 26 12:36:22 ubuntuserver1 mysqld: diagnose the problem, but since we have already crashed, Nov 26 12:36:22 ubuntuserver1 mysqld: something is definitely wrong and this may fail. Nov 26 12:36:22 ubuntuserver1 mysqld: Nov 26 12:36:22 ubuntuserver1 mysqld: Server version: 10.0.14-MariaDB-1~trusty-wsrep-log Nov 26 12:36:22 ubuntuserver1 mysqld: key_buffer_size=134217728 Nov 26 12:36:22 ubuntuserver1 mysqld: read_buffer_size=2097152 Nov 26 12:36:22 ubuntuserver1 mysqld: max_used_connections=1 Nov 26 12:36:22 ubuntuserver1 mysqld: max_threads=102 Nov 26 12:36:22 ubuntuserver1 mysqld: thread_count=3 Nov 26 12:36:22 ubuntuserver1 mysqld: It is possible that mysqld could use up to Nov 26 12:36:22 ubuntuserver1 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759897 K bytes of memory Nov 26 12:36:22 ubuntuserver1 mysqld: Hope that's ok; if not, decrease some variables in the equation. Nov 26 12:36:22 ubuntuserver1 mysqld: Nov 26 12:36:22 ubuntuserver1 mysqld: Thread pointer: 0x0x7f62d0e9b008 Nov 26 12:36:22 ubuntuserver1 mysqld: Attempting backtrace. You can use the following information to find out Nov 26 12:36:22 ubuntuserver1 mysqld: where mysqld died. If you see no messages after this, something went Nov 26 12:36:22 ubuntuserver1 mysqld: terribly wrong... Nov 26 12:36:22 ubuntuserver1 mysqld: stack_bottom = 0x7f6309ff0df0 thread_stack 0x48000 Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f630abb6d8e] Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x457)[0x7f630a6f33e7] Nov 26 12:36:22 ubuntuserver1 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f6308ea2340] Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(_Z18view_store_optionsP3THDP10TABLE_LISTP6String+0x84)[0x7f630a5cf994] Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(_Z24wsrep_to_isolation_beginP3THDPcS1_PK10TABLE_LIST+0x822)[0x7f630a6921b2] Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x6fea)[0x7f630a56fd8a] Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(+0x40d977)[0x7f630a572977] Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x217f)[0x7f630a57519f] Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(_Z10do_commandP3THD+0x20f)[0x7f630a575a8f] Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1fb)[0x7f630a643deb] Nov 26 12:36:22 ubuntuserver1 mysqld: /usr/sbin/mysqld(handle_one_connection+0x40)[0x7f630a643fd0] Nov 26 12:36:22 ubuntuserver1 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f6308e9a182] Nov 26 12:36:22 ubuntuserver1 mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f63085bcfbd] Nov 26 12:36:22 ubuntuserver1 mysqld: Nov 26 12:36:22 ubuntuserver1 mysqld: Trying to get some variables. Nov 26 12:36:22 ubuntuserver1 mysqld: Some pointers may be invalid and cause the dump to abort. Nov 26 12:36:22 ubuntuserver1 mysqld: Query (0x7f62d0f38106): is an invalid pointer Nov 26 12:36:22 ubuntuserver1 mysqld: Connection ID (thread ID): 48 Nov 26 12:36:22 ubuntuserver1 mysqld: Status: NOT_KILLED Nov 26 12:36:22 ubuntuserver1 mysqld: Nov 26 12:36:22 ubuntuserver1 mysqld: 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 Nov 26 12:36:22 ubuntuserver1 mysqld: Nov 26 12:36:22 ubuntuserver1 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Nov 26 12:36:22 ubuntuserver1 mysqld: information that should help you find out what is causing the crash. Nov 26 12:36:22 ubuntuserver1 mysqld_safe: Number of processes running now: 0 Nov 26 12:36:22 ubuntuserver1 mysqld_safe: WSREP: not restarting wsrep node automatically Nov 26 12:36:22 ubuntuserver1 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
I'm not an expert but it probably only an unsupported SQL statement on Galera cluster.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
http://lists.askmonty.org/pipermail/commits/2015-January/007226.html