[MCOL-4118] Crash on MEDIUM BLOB insert Created: 2020-06-26  Updated: 2023-11-17  Resolved: 2022-10-12

Status: Closed
Project: MariaDB ColumnStore
Component/s: MDB Plugin
Affects Version/s: None
Fix Version/s: 23.02.1

Type: Bug Priority: Minor
Reporter: Todd Stoffel (Inactive) Assignee: David Hall (Inactive)
Resolution: Fixed Votes: 1
Labels: None


 Description   

Steps to reproduce:

docker run -d -p 3306:3306 -e SKIP_OAM_INIT=1 -e ANALYTICS_ONLY=0 -e USE_S3_STORAGE=0 --name mcs_container mariadb/skysql-enterprise-columnstore-handoff:1.4.4-WITH-BACKUP

docker exec -it mcs_container bash

cd /tmp
 
wget https://townsquare.media/site/385/files/2019/07/bunny-rabbit.jpg

mariadb>
 
CREATE DATABASE test;
 
USE test;
 
CREATE TABLE `innodb_image` (
  `img` MEDIUMBLOB DEFAULT NULL
) ENGINE=innodb DEFAULT CHARSET=utf8;
 
CREATE TABLE `columnstore_image` (
  `img` MEDIUMBLOB DEFAULT NULL
) ENGINE=columnstore DEFAULT CHARSET=utf8;
 
INSERT INTO innodb_image VALUES (LOAD_FILE('/tmp/bunny-rabbit.jpg'));
 
INSERT INTO columnstore_image SELECT * FROM innodb_image;

200626 19:34:26 [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.4.13-7-MariaDB-enterprise
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=8
max_threads=153
thread_count=14
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467760 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f0584007b18
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 = 0x7f05d4064cf0 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55beaf7a6d9e]
/usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55beaf22b94f]
sigaction.c:0(__restore_rt)[0x7f05f3734630]
/usr/lib64/mysql/plugin/ha_columnstore.so(_Z28ha_mcs_impl_write_batch_row_PKhP5TABLERN11cal_impl_if19cal_connection_infoE+0x3c8)[0x7f05ec0bb768]
/usr/lib64/mysql/plugin/ha_columnstore.so(_Z21ha_mcs_impl_write_rowPKhP5TABLEm+0x2cc)[0x7f05ec09346c]
/usr/lib64/mysql/plugin/ha_columnstore.so(_ZN6ha_mcs9write_rowEPKh+0x1f)[0x7f05ec08e36f]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPKh+0x2c8)[0x55beaf236d38]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x69)[0x55beaefed889]
/usr/sbin/mysqld(_ZN13select_insert9send_dataER4ListI4ItemE+0xe0)[0x55beaefee390]
/usr/sbin/mysqld(+0x6eb44f)[0x55beaf05d44f]
/usr/sbin/mysqld(+0x6dae9c)[0x55beaf04ce9c]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x1be)[0x55beaf05251e]
/usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0xc73)[0x55beaf07e813]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x33)[0x55beaf07ea43]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x186)[0x55beaf07cc96]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1d7)[0x55beaf07d807]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x80f8)[0x55beaf027ac8]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1fb)[0x55beaf0289db]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x199f)[0x55beaf02abaf]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x109)[0x55beaf02c1f9]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x221)[0x55beaf10cb31]
/usr/sbin/mysqld(handle_one_connection+0x3d)[0x55beaf10cbed]
pthread_create.c:0(start_thread)[0x7f05f372cea5]
/lib64/libc.so.6(clone+0x6d)[0x7f05f14f98dd]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f0584016ff0): is an invalid pointer
Connection ID (thread ID): 19
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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=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: insert into columnstore_image SELECT * FROM innodb_image
 
Writing a core file...
Working directory at /var/lib/mysql
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             unlimited            unlimited            processes
Max open files            1048576              1048576              files
Max locked memory         83968000             83968000             bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       11854                11854                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



 Comments   
Comment by Gregory Dorman (Inactive) [ 2020-06-26 ]

In case anyone is interested... In both innodb and columnstore cases, if you select img into outfile, you do not get the original (the file is bigger). And it cannot be rendered by tools which display jpg files...

Comment by David Hall (Inactive) [ 2022-10-12 ]

I tested this in 22.08.2 and it worked and did not crash.

Generated at Thu Feb 08 02:47:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.