[MDEV-10147] server crashes sporadically in create_view_field Created: 2016-05-27 Updated: 2020-08-25 Resolved: 2018-06-07 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Views |
| Affects Version/s: | 10.1.14, 5.5, 10.0, 10.1, 10.1.31, 10.2, 10.3 |
| Fix Version/s: | 5.5.61, 10.0.36, 10.1.34, 10.2.16, 10.3.8 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Kevin Schmeichel | Assignee: | Oleksandr Byelkin |
| Resolution: | Fixed | Votes: | 3 |
| Labels: | None | ||
| Environment: |
Linux Mint 17.3 |
||
| Description |
|
Hi- I'm experiencing occasionally crashes in a query that joins a few tables, including a join to a view. From what I can tell from the stack trace, the problem may have something to do with the view. This query normally works fine, and when I run it in the command line client it is very fast. However, under relatively heavy load, especially when I configure my connection pool to contain only a single connection, I get a crash - always on the same query. The stack trace is below, please let me know if there is any additional information I can provide.
Thanks, |
| Comments |
| Comment by Elena Stepanova [ 2016-05-28 ] | |||||||
|
Can you provide the query since you have already located it, and
or
for all involved tables and views? Please also attach your cnf file(s). Regarding reproducing it locally on your machine, if you can afford experimenting, please try to execute the query via a prepared statement, and if it does not crash at the first attempt, execute it twice more. That is, do the following:
| |||||||
| Comment by Elena Stepanova [ 2016-06-25 ] | |||||||
|
schmeic, hi, | |||||||
| Comment by Kevin Schmeichel [ 2016-09-07 ] | |||||||
|
Sorry I was unable to provide further info, got really busy at work. Just wanted to add that this keeps happening with different queries, but all have in common the fact that I'm joining to a view. At this point, I've decided to just change all queries that joined view to just include the view joins inline. This seems to always work. Here is a stack trace, crashing in the same place, but a bit different stack: stack_bottom = 0x7f576a3fd0b8 thread_stack 0x48400 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=off | |||||||
| Comment by Kevin Schmeichel [ 2016-09-07 ] | |||||||
|
By the way, I did try running this as prepared statement as describe above, and was unable to make it crash. It seems pretty random, but happens about once or twice a day. | |||||||
| Comment by Chris Calender (Inactive) [ 2018-06-06 ] | |||||||
|
While the stack traces differ, they are similar in some places, thus we wondered if this might be similar/related to: | |||||||
| Comment by Oleksandr Byelkin [ 2018-06-07 ] | |||||||
|
The fix pushed into 5.5: Catch of OOM situation. |