[MDEV-21884] MariaDB with Spider crashes on a query Created: 2020-03-06 Updated: 2020-05-15 Resolved: 2020-04-17 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Platform Debian, Server, Storage Engine - Spider |
| Affects Version/s: | 10.3.22 |
| Fix Version/s: | 10.3.23, 10.4.13, 10.5.3 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Jan Kristek | Assignee: | Kentoku Shiba (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | spider | ||
| Environment: |
Ubuntu with MariaDB in the mariadb:10.3 container |
||
| Attachments: |
|
| Description |
|
I have a set up with a Spider node and three backend nodes with InnoDB. When I run the following query: SELECT * FROM ARCHIVE a the spider crashes with the log below. I am not able to isolate the data, as I have quite a big dataset in the backends. Version: '10.3.22-MariaDB-1:10.3.22+maria~bionic' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution 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 Server version: 10.3.22-MariaDB-1:10.3.22+maria~bionic Thread pointer: 0x7ffaf0000c08 Trying to get some variables. 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,split_materialized=on The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains |
| Comments |
| Comment by Jan Kristek [ 2020-03-09 ] |
|
It seems to work well with the default setting of Spider. Starts crashing when I set spider_bgs_mode = 2. Maybe I have to set something in addition (buffer limit, chunk size, etc...)? Or use a different bgs mode? |
| Comment by Jan Kristek [ 2020-03-09 ] |
|
I managed to cut out some data causing the issue. Steps to reproduce:
If you would like to re-reproduce the crash, sometimes deleting the containers and volumes content first might be needed. archback.sql |
| Comment by Kentoku Shiba (Inactive) [ 2020-04-16 ] |
|
Fixed at the following commit. |
| Comment by Jan Kristek [ 2020-05-15 ] |
|
I have tested it now and no failure. Thank you very much, Kentoku! |