MariaDB Crashes on large DB imports

We have tried importing our 46GB database in via mysqlimport and via standard mysql but both time it crashses. Here is the log:

Code:

150325 19:16:33 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.17-MariaDB'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
150325 20:10:08 [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 http://kb.askmonty.org/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.0.17-MariaDB
key_buffer_size=53687091200
read_buffer_size=65536
max_used_connections=16
max_threads=302
thread_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 52493015 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x7f433fe91008
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 = 0x7f53dfd53d30 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb743db]
/usr/sbin/mysqld(handle_fatal_signal+0x398)[0x726a38]
/lib64/libpthread.so.0[0x36e860f710]
/lib64/libpthread.so.0(pthread_cond_signal+0x44)[0x36e860be34]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f42fb41d020): is an invalid pointer
Connection ID (thread ID): 260
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

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.
150325 20:10:08 mysqld_safe Number of processes running now: 0
150325 20:10:08 mysqld_safe mysqld restarted

---

 

It isn't on that partition anymore.

 

I understand that. Was looking for community feedback more than anything else. BTW, we replaced MariaDB with Percona and it imported with no issue. So there is a bug somewhere.

 

I would be interested to know if you have any large database sites using MyISAM running MariaDB 10 though

 

We ran into an issue with max_seeks_for_key = 1000 which was a change from how our Percona server was setup.

Mike spent a few days troubleshooting and finally figured out our slow query (7 seconds) was due to this.

So if you run a large XenForo forum and are seeing slow query issues with MariaDB, this is likely the issue.

Other than that the database imported fine and things seem to be running smoothly now.