[MDEV-14314] Crash with massive parall inserts Created: 2017-11-07  Updated: 2017-11-23  Resolved: 2017-11-23

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - RocksDB
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Anders Karlsson Assignee: Andrii Nikitin (Inactive)
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-14290 Mariadb 10.2 RocksDB crash on binlog ... Closed

 Description   

Running a program that inserts lots of data in parallel. Data is array inserts with 100 elements per array. Table structure:

CREATE TABLE `cdr` (
 `calldate` datetime NOT NULL default '0000-00-00 00:00:00',
 `clid` varchar(80) NOT NULL default '',
 `src` varchar(80) NOT NULL default '',
 `dst` varchar(80) NOT NULL default '',
 `dcontext` varchar(80) NOT NULL default '',
 `channel` varchar(80) NOT NULL default '',
 `dstchannel` varchar(80) NOT NULL default '',
 `lastapp` varchar(80) NOT NULL default '',
 `lastdata` varchar(80) NOT NULL default '',
 `duration` int(11) NOT NULL default '0',
 `billsec` int(11) NOT NULL default '0',
 `disposition` varchar(45) NOT NULL default '',
 `amaflags` int(11) NOT NULL default '0',
 `accountcode` varchar(20) NOT NULL default '',
 `userfield` varchar(255) NOT NULL default '',
 `uniqueid` VARCHAR(32) NOT NULL default '',
 `linkedid` VARCHAR(32) NOT NULL default '',
 `sequence` VARCHAR(32) NOT NULL default '',
 `peeraccount` VARCHAR(32) NOT NULL default ''
) ENGINE=RocksDB;

After inserting several hundred arrays of data (maybe 700k rows in total) MariaDB crashes. In the error log I get:

2017-11-07 10:01:21 140336996464384 [ERROR] Invalid (old?) table or database name '.rocksdb'
171107 10:02:52 [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.2.10-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=12
max_threads=153
thread_count=19
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467220 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7fa2500009a8
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 = 0x7fa2cc076e50 thread_stack 0x49000
/disk2/local/mariadb-10.2.10-linux-systemd-x86_64/bin/mysqld(my_print_stacktrace+0x2e)[0x55931c69787e]
/disk2/local/mariadb-10.2.10-linux-systemd-x86_64/bin/mysqld(handle_fatal_signal+0x30d)[0x55931c1172ed]
/lib64/libpthread.so.0(+0xf5e0)[0x7fa2d27765e0]
/disk2/local/mariadb-10.2.10-linux-systemd-x86_64/bin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0xa0)[0x55931c1f6390]
/disk2/local/mariadb-10.2.10-linux-systemd-x86_64/bin/mysqld(binlog_background_thread+0x303)[0x55931c1f6993]
/lib64/libpthread.so.0(+0x7e25)[0x7fa2d276ee25]
/lib64/libc.so.6(clone+0x6d)[0x7fa2d1e8734d]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0): is an invalid pointer
Connection ID (thread ID): 6
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:
 
171107 10:02:52 mysqld_safe Number of processes running now: 0



 Comments   
Comment by Andrii Nikitin (Inactive) [ 2017-11-17 ]

According to MDEV-14290 and my tests the crash happens on any binlog rotation, so I will mark this as duplicate

Generated at Thu Feb 08 08:12:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.