Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
-
None
Description
This was original opened against Columnstore using build 1.2.5. CS Eng reported it was a crash in InnoDB. May need to be an MDEV ticket. So opening this ticket from MCOL-3740.
Customer reporting that everytime they do a systemShutdown, the mysqld_safe and mysql still show to be running after shutdown is completed.
I worked with them to just try running the below commands to see what happens when nothing else of going on, and it still crashed
/usr/local/mariadb/columnstore/mysql/mysql-Columnstore start
|
/usr/local/mariadb/columnstore/mysql/mysql-Columnstore stop
|
/usr/local/mariadb/columnstore/mysql/mysql-Columnstore status
|
Log files always shows the same thing,
Event Scheduler: Purging the queue. 21 events
|
200123 13:48:41 [ERROR] mysqld got signal 11 ;
|
 |
/usr/local/mariadb/columnstore/mysql//bin/mysqld (initiated by: unknown): Normal shutdown
|
2020-01-23 13:48:41 0 [Note] Event Scheduler: Killing the scheduler thread, thread id 6
|
2020-01-23 13:48:41 0 [Note] Event Scheduler: Waiting for the scheduler thread to reply
|
2020-01-23 13:48:41 0 [Note] Event Scheduler: Stopped
|
2020-01-23 13:48:41 0 [Note] Event Scheduler: Purging the queue. 21 events
|
200123 13:48:41 [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.3.16-MariaDB-log
|
key_buffer_size=536870912
|
read_buffer_size=4194304
|
max_used_connections=0
|
max_threads=65537
|
thread_count=7
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 537414652 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
Thread pointer: 0x0
|
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 = 0x0 thread_stack 0x80000
|
/usr/local/mariadb/columnstore/mysql//bin/mysqld(my_print_stacktrace+0x29)[0x55b20cbe6279]
|
mysys/stacktrace.c:270(my_print_stacktrace)[0x55b20c71eb6f]
|
sigaction.c:0(__restore_rt)[0x7f9c220485d0]
|
/usr/local/mariadb/columnstore/mysql//bin/mysqld(+0xa1632a)[0x55b20c9eb32a]
|
btr/btr0cur.cc:1375(btr_cur_search_to_nth_level_func(dict_index_t*, unsigned long, dtuple_t const*, page_cur_mode_t, unsigned long, btr_cur_t*, rw_lock_t*, char const*, unsigned int, mtr_t*, unsigned long))[0x55b20c9631ae]
|
include/btr0pcur.ic:511(btr_pcur_open_with_no_init_func)[0x55b20c9696fd]
|
row/row0sel.cc:1681(row_sel(sel_node_t*, que_thr_t*))[0x55b20c96b17b]
|
row/row0sel.cc:2347(row_sel_step(que_thr_t*))[0x55b20c92007b]
|
que/que0que.cc:1018(que_thr_step)[0x55b20caa5695]
|
fts/fts0sql.cc:221(fts_eval_sql(trx_t*, que_fork_t*))[0x55b20ca8f5f4]
|
fts/fts0fts.cc:2684(fts_cmp_set_sync_doc_id(dict_table_t const*, unsigned long, unsigned long, unsigned long*))[0x55b20ca8f8dc]
|
fts/fts0fts.cc:4193(fts_sync_commit(fts_sync_t*))[0x55b20ca92fca]
|
fts/fts0fts.cc:4391(fts_sync(fts_sync_t*, bool, bool, bool) [clone .part.105])[0x55b20ca96942]
|
fts/fts0opt.cc:2782(fts_optimize_sync_table(unsigned long))[0x55b20ca9c785]
|
pthread_create.c:0(start_thread)[0x7f9c22040dd5]
|
/lib64/libc.so.6(clone+0x6d)[0x7f9c1ffecead]
|
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.
|
Writing a core file...
|
Working directory at /usr/local/mariadb/columnstore/mysql/db
|
Resource Limits:
|
Limit Soft Limit Hard Limit Units
|
Max cpu time unlimited unlimited seconds
|
Max file size unlimited unlimited bytes
|
Max data size unlimited unlimited bytes
|
Max stack size 8388608 unlimited bytes
|
Max core file size 0 unlimited bytes
|
Max resident set unlimited unlimited bytes
|
Max processes 982518 982518 processes
|
Max open files 65535 65535 files
|
Max locked memory 65536 65536 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 982518 982518 signals
|
Max msgqueue size 819200 819200 bytes
|
Max nice priority 0 0
|
Max realtime priority 0 0
|
Max realtime timeout unlimited unlimited us
|
Core pattern: core
|
------------------------
From customer
There are 21 events in the mysql.event table that are enabled
i tried turning off event scheduler but that didn't help still crashed on shutdown
Attachments
Issue Links
- relates to
-
MDEV-12266 Reduce the number of InnoDB tablespace lookups
-
- Closed
-
-
-
- Closed
-