[MDEV-13835] Crash when flushing tables with Connect Created: 2017-09-18  Updated: 2017-11-06  Resolved: 2017-11-06

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Connect
Affects Version/s: 10.2.8
Fix Version/s: 10.2.9

Type: Bug Priority: Major
Reporter: Antonio Fernandes Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Environment:

Centos 6.9 x86_64
kernel 2.6.32-696.6.3.el6.x86_64



 Description   

I've got this crash when running FLUSH TABLES:

170918 15:00:06 [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.8-MariaDB-log
key_buffer_size=1073741824
read_buffer_size=4194304
max_used_connections=35
max_threads=83
thread_count=42
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2070214 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f3e98110398
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 = 0x7f411297ad80 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f411371d9ab]
/usr/sbin/mysqld(handle_fatal_signal+0x4d5)[0x7f41131b4405]
/lib64/libpthread.so.0(+0x3035c0f7e0)[0x7f41126df7e0]
/usr/lib64/mysql/plugin/ha_connect.so(_Z13CntCloseTableP7_globalP3TDBbb+0x33)[0x7f40b7cfbdd3]
/usr/lib64/mysql/plugin/ha_connect.so(_ZN10ha_connect10CloseTableEP7_global+0x29)[0x7f40b7cef539]
/usr/sbin/mysqld(_Z8closefrmP5TABLE+0x131)[0x7f41130d06e1]
/usr/sbin/mysqld(_Z8tc_purgeb+0x69)[0x7f4113163559]
/usr/sbin/mysqld(_Z19close_cached_tablesP3THDP10TABLE_LISTbm+0x87)[0x7f4112ff3a77]
/usr/sbin/mysqld(_Z20reload_acl_and_cacheP3THDyP10TABLE_LISTPi+0x31e)[0x7f411311595e]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1047)[0x7f4113035457]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x29a)[0x7f411303c79a]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1d3e)[0x7f411303eb6e]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x14e)[0x7f411303f14e]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x16f)[0x7f41130fbf4f]
/usr/sbin/mysqld(handle_one_connection+0x44)[0x7f41130fc074]
/lib64/libpthread.so.0(+0x3035c07aa1)[0x7f41126d7aa1]
/lib64/libc.so.6(clone+0x6d)[0x7f4110defbcd]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f3e9805f440): FLUSH TABLES
 
Connection ID (thread ID): 112966
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.
170918 15:00:08 mysqld_safe Number of processes running now: 0
170918 15:00:08 mysqld_safe mysqld restarted

I didn't have anything wierd running on my local server...

Thanks,
António Fernandes



 Comments   
Comment by Elena Stepanova [ 2017-09-30 ]

What kind of CONNECT tables do you have and use? Are there many? If not, would you be able to provide definitions?
Is it reproducible, or was it one-time occurrence?
Was there anything suspicious in the error log before the crash?

Comment by Antonio Fernandes [ 2017-10-07 ]

Hello Elena,

I've since upgraded to 10.2.9 and, so far, no crash.

I'm using a zipped csv file accessed through Connect. Just one file and it's just a read-only table.

Here's the schema:
```
CREATE TABLE `tbl_peugeot_precario_connect` (
`Diffusion_type` varchar(3) NOT NULL `flag`=0,
`Diffusion_date` date NOT NULL `date_format`='YYYYMMDD' `flag`=3,
`Price_date` date NOT NULL `date_format`='YYYYMMDD' `flag`=11,
`Sales_organization` varchar(4) NOT NULL `flag`=19,
`Country` varchar(3) NOT NULL `flag`=23,
`Price_list` varchar(2) NOT NULL `flag`=26,
`Pricetable` varchar(1) NOT NULL `flag`=28,
`Currency` varchar(5) NOT NULL `flag`=29,
`Referencia` varchar(18) NOT NULL `flag`=34,
`Designacao` varchar(15) NOT NULL `flag`=52,
`Designacao_FR` varchar(15) NOT NULL `flag`=67,
`Division` varchar(1) NOT NULL `flag`=82,
`Modelo` varchar(3) NOT NULL `flag`=83,
`Tax_class` varchar(1) NOT NULL `flag`=86,
`Hide_catalogue_price` varchar(1) NOT NULL `flag`=87,
`Dealer_net_price_(unitary)` double(12,2) NOT NULL `field_format`='ZN2' `flag`=88,
`PVP` double(12,2) NOT NULL `field_format`='ZN2' `flag`=99,
`Tipo_Substituicao` varchar(1) NOT NULL `flag`=110,
`Lista` varchar(7) NOT NULL `flag`=111,
`Material_replaced_code` varchar(18) NOT NULL `flag`=118,
`Unidade_Venda` double(5,0) NOT NULL `field_format`='Z' `flag`=136,
`Gross_Weight` double(15,0) NOT NULL `field_format`='Z' `flag`=141,
`Codigo_Desconto` varchar(2) NOT NULL `flag`=156,
`Recall_group` varchar(3) NOT NULL `flag`=158,
`Commodity_code` varchar(17) NOT NULL `flag`=161,
`Index` varchar(4) NOT NULL `flag`=178,
`Segment` varchar(4) NOT NULL `flag`=182,
`Price_familly` varchar(5) NOT NULL `flag`=186,
`Familia_Marketing` varchar(5) NOT NULL `flag`=191,
`External_material_group` varchar(1) NOT NULL `flag`=196,
`Referencia_Sobretaxa` varchar(18) NOT NULL `flag`=197,
`Valor_Sobretaxa` double(11,3) NOT NULL `field_format`='ZN2' `flag`=215,
`Exchange_type` varchar(1) NOT NULL `flag`=226,
`Origin_of_the_part` varchar(1) NOT NULL `flag`=227,
`Part_local_storage_code` varchar(1) NOT NULL `flag`=228,
`Referencia_Substituida` varchar(13) NOT NULL `flag`=229,
`Trading_code` varchar(3) NOT NULL `flag`=242,
`Organic_group` varchar(2) NOT NULL `flag`=245,
`Quantity_material_1` varchar(6) NOT NULL `flag`=247,
`Material_2` varchar(18) NOT NULL `flag`=253,
`Quantity_material_2` varchar(6) NOT NULL `flag`=271,
`Material_3` varchar(18) NOT NULL `flag`=277,
`Quantity_material_3` varchar(6) NOT NULL `flag`=295,
`Material_4` varchar(18) NOT NULL `flag`=301,
`Quantity_material_4` varchar(6) NOT NULL `flag`=319,
`Material_5` varchar(18) NOT NULL `flag`=325,
`Quantity_material_5` varchar(6) NOT NULL `flag`=343,
`Material_6` varchar(18) NOT NULL `flag`=349,
`Quantity_material_6` varchar(6) NOT NULL `flag`=367,
`Sales_part_status` varchar(2) NOT NULL `flag`=373,
`Availibility_on_catalogue` varchar(3) NOT NULL `flag`=375,
`Material_type_of_modification_detected` varchar(1) NOT NULL `flag`=378,
`Designation_3` varchar(15) NOT NULL `flag`=379,
`Designation_4` varchar(15) NOT NULL `flag`=394,
`Sales_frequency` varchar(2) NOT NULL `flag`=409,
`Procurement_family` varchar(3) NOT NULL `flag`=411,
`Filler` varchar(36) NOT NULL `flag`=414,
`UTC` varchar(5) NOT NULL `flag`=450,
`Pneumatic_family` varchar(3) NOT NULL `flag`=455,
`Pneumatic_size` varchar(26) NOT NULL `flag`=458,
`Pneumatic_commercial_name` varchar(31) NOT NULL `flag`=484,
`Length` double(15,3) NOT NULL `field_format`='ZN3' `flag`=515,
`Item_width` double(15,3) NOT NULL `field_format`='ZN3' `flag`=530,
`Height` double(15,3) NOT NULL `field_format`='ZN3' `flag`=545,
`Volume` double(15,3) NOT NULL `field_format`='ZN3' `flag`=560,
`Filler_2` varchar(75) NOT NULL `flag`=575
) ENGINE=CONNECT DEFAULT CHARSET=utf8 `READONLY`=1 `COMPRESS`=1 `table_type`=DOS `file_name`='tbl_peugeot_precario_connect.txt.gz'
```

For the time being I was unable to reproduce it.

As for the log, nothing out of the ordinary...

Best regards,
António

Comment by Elena Stepanova [ 2017-10-08 ]

There have been changes in Connect engine in 10.2.9 comparing to 10.2.8, so let's wait to see if you encounter the problem again. Please let us know if you do, I will keep the item open for now.

Comment by Elena Stepanova [ 2017-11-05 ]

ampf, have you ever had the problem after upgrading?

Comment by Antonio Fernandes [ 2017-11-06 ]

Hi Elena,

Thanks for asking.

So far, no crashes

I've since upgraded to 10.2.10 and all good.

Comment by Elena Stepanova [ 2017-11-06 ]

ampf, thanks.
I will then close it for now as fixed in 10.2.9; please comment if the problem resurfaces. Since there have been no commits in scope of this report, it can be re-opened if necessary.

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