Bug #107889 sometimes. when executing UNION querying occurs Signal 11 occures

• Submitted: 15 Jul 2022 2:14
• Modified: 15 Jul 2022 12:35
• Reporter: 박다래 박
• Status: Can't repeat
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 8.0.29
• OS: Linux (Amzon RDS for mysql)
• CPU Architecture: Any

[15 Jul 2022 2:14] 박다래 박

Description:
Our system uses Amazon RDS for MySQL.
and MySql VERSION is 8.0.29.
when below query was executing, signal 11 occurs and reboot mysql.
I think this is mysql's bug related optimizer.

===================[SQL]=================
select
    `d_directory`.`parent_dir` as `parent_dir`,
    `d_directory`.`name` as `name`,
    `d_directory`.`dir_gubun` as `dir_gubun`,
    `d_directory`.`job_id` as `job_id`,
    `d_directory`.`version` as `version`,
    `d_directory`.`modify_date` as `modify_date`,
    `d_directory`.`del_flag` as `del_flag`,
    `d_directory`.`server_type` as `server_type`,
    `d_directory`.`errorincharge` as `errorincharge`,
    `d_directory`.`work_interval` as `work_interval`,
    `d_directory`.`search_group` as `search_group`,
    `d_directory`.`job_alias` as `job_alias`
from
    `d_directory`
union
select
    `d_dir_history`.`parent_dir` as `parent_dir`,
    `d_dir_history`.`name` as `name`,
    `d_dir_history`.`dir_gubun` as `dir_gubun`,
    `d_dir_history`.`job_id` as `job_id`,
    `d_dir_history`.`version` as `version`,
    `d_dir_history`.`modify_date` as `modify_date`,
    `d_dir_history`.`del_flag` as `del_flag`,
    `d_dir_history`.`server_type` as `server_type`,
    `d_dir_history`.`errorincharge` as `errorincharge`,
    `d_dir_history`.`work_interval` as `work_interval`,
    `d_dir_history`.`search_group` as `search_group`,
    `d_dir_history`.`job_alias` as `job_alias`
from
    `d_dir_history`;
==============================================================================

But this phenomenon occurs sometimes.
I attahced the mysql error log.

03:19:38 UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x1549c335b000
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 = 154997b71460 thread_stack 0x40000
/rdsdbbin/mysql/bin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2e) [0x2097dae]
/rdsdbbin/mysql/bin/mysqld(print_fatal_signal(int)+0x2bb) [0x102057b]
/rdsdbbin/mysql/bin/mysqld(handle_fatal_signal+0xa5) [0x1020625]
/lib64/libpthread.so.0(+0x118e0) [0x154ca3b998e0]
/rdsdbbin/mysql/bin/mysqld(JOIN::update_sargable_from_const(SARGABLE_PARAM*)+0x20) [0xebb2c0]
/rdsdbbin/mysql/bin/mysqld(JOIN::make_join_plan()+0x6dc) [0xece5fc]
/rdsdbbin/mysql/bin/mysqld(JOIN::optimize(bool)+0xf94) [0xed0724]
/rdsdbbin/mysql/bin/mysqld(Query_block::optimize(THD*, bool)+0xae) [0xf3100e]
/rdsdbbin/mysql/bin/mysqld(Query_expression::optimize(THD*, TABLE*, bool, bool)+0x7e) [0xfa875e]
/rdsdbbin/mysql/bin/mysqld(TABLE_LIST::optimize_derived(THD*)+0x3f) [0x1389a9f]
/rdsdbbin/mysql/bin/mysqld(JOIN::optimize(bool)+0x3e3) [0xecfb73]
/rdsdbbin/mysql/bin/mysqld(Query_block::optimize(THD*, bool)+0xae) [0xf3100e]
/rdsdbbin/mysql/bin/mysqld(Query_expression::optimize(THD*, TABLE*, bool, bool)+0x7e) [0xfa875e]
/rdsdbbin/mysql/bin/mysqld(Sql_cmd_dml::execute_inner(THD*)+0x30) [0xf2fe30]
/rdsdbbin/mysql/bin/mysqld(Sql_cmd_dml::execute(THD*)+0x16e) [0xf2f56e]
/rdsdbbin/mysql/bin/mysqld(mysql_execute_command(THD*, bool)+0x9b0) [0xed9cf0]
/rdsdbbin/mysql/bin/mysqld(dispatch_sql_command(THD*, Parser_state*)+0x3de) [0xedda0e]
/rdsdbbin/mysql/bin/mysqld(dispatch_command(THD*, COM_DATA const*, enum_server_command)+0xed5) [0xedee45]
/rdsdbbin/mysql/bin/mysqld(do_command(THD*)+0x10f) [0xee107f]
/rdsdbbin/mysql/bin/mysqld() [0x1011e30]
/rdsdbbin/mysql/bin/mysqld() [0x262b1e5]
/lib64/libpthread.so.0(+0x744b) [0x154ca3b8f44b]
/lib64/libc.so.6(clone+0x3f) [0x154ca337440f]

How to repeat:
Actually, I can not explain how to repeat....

[15 Jul 2022 12:35] MySQL Verification Team

Hi Mr. 박다래 박,

Thank you for your bug report.

However, ........

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php 

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.  

Thank you for your interest in MySQL.