[MDEV-20041] MariaDB Error Log Content Created: 2019-07-11 Updated: 2019-07-21 Resolved: 2019-07-21 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Backup, Debug, Replication, Storage Engine - InnoDB |
| Affects Version/s: | 10.0.17 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Gong Seonsik | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | crash, replication | ||
| Issue Links: |
|
||||||||
| Description |
|
Server version: 10.0.17-MariaDB-log Thread pointer: 0x0x7f846522e008 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 |
| Comments |
| Comment by Alice Sherepa [ 2019-07-11 ] |
|
Is it suitable for you to upgrade to the recent version of MariaDB (for 10.0 it is 10.0.38) and see if the crash is still present there? A lot of bugs were fixed since 10.0.17 |
| Comment by Gong Seonsik [ 2019-07-12 ] |
|
I did not upgrade. |
| Comment by Alice Sherepa [ 2019-07-12 ] |
|
Is that crash repeatable for you or did it happen only once? |
| Comment by Gong Seonsik [ 2019-07-15 ] |
|
The collision was not repetitive. |
| Comment by Elena Stepanova [ 2019-07-21 ] |
|
10.0 release line is not supported any longer. Also, the last 10.0 release was 10.0.38, which is 20 releases and almost 4 years ahead of the one you are using. There had been numerous bugfixes since 2015, including the area which your stack trace points at. Without a test case, it is impossible to say which exactly bug you have encountered, and whether it has been fixed. Please upgrade to the latest release of a supported release line (10.1, 10.2, 10.3, 10.4). |