INSERT IGNORE ... SELECT 쿼리 사용 중 got signal 6 가 발생하여 원인에 대해 문의

2022-01-02 00:30:49 7fc85b3ff700 InnoDB: Assertion failure in thread 140498501105408 in file btr0cur.cc line 330
InnoDB: Failing assertion: page_is_comp(get_block->frame) == page_is_comp(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
220102 0:30:49 [ERROR] mysqld got signal 6 ;
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.1.44-MariaDB
key_buffer_size=33554432
read_buffer_size=1048576
max_used_connections=25
max_threads=2002
thread_count=7
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4174416 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fc847c4c008
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 = 0x7fc85b3feddf thread_stack 0x100000
sql/sql_string.h:315(~String)[0xc28c5e]
/data/maria/bin/mysqld(handle_fatal_signal+0x4bf)[0x78a5ff]
sigaction.c:0(__restore_rt)[0x7fcad94527e0]
/lib64/libc.so.6(gsignal+0x35)[0x7fcad8313495]
/lib64/libc.so.6(abort+0x175)[0x7fcad8314c75]
sql/sql_list.h:232(base_list::push_back(void*, st_mem_root*))[0xaf712b]
sql/opt_subselect.cc:1694(convert_subq_to_sj)[0xafa3a7]
sql/table.cc:4850(TABLE_LIST::set_insert_values(st_mem_root*))[0xa7a52c]
sql/table.cc:1270(TABLE_SHARE::init_from_binary_frm_image(THD*, bool, unsigned char const*, unsigned long))[0xa7b85c]
sql/table.cc:1050(TABLE_SHARE::init_from_binary_frm_image(THD*, bool, unsigned char const*, unsigned long))[0xa7bf43]
sql/tztime.cc:1334(Time_zone_offset)[0xa8712d]
psi/mysql_file.h:1053(inline_mysql_file_open)[0x9e5604]
/data/maria/bin/mysqld(_ZN7handler12ha_write_rowEPh+0x214)[0x794114]
/data/maria/bin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x61)[0x5a7b21]
/data/maria/bin/mysqld(_ZN13select_insert9send_dataER4ListI4ItemE+0xd5)[0x5a8415]
/data/maria/bin/mysqld[0x603f20]
/data/maria/bin/mysqld[0x615a7f]
/data/maria/bin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x17a)[0x615dda]
/data/maria/bin/mysqld[0x6164fd]
/data/maria/bin/mysqld(_ZN4JOIN10exec_innerEv+0xc70)[0x620630]
/data/maria/bin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1ec)[0x61eb9c]
/data/maria/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x258)[0x622cb8]
/data/maria/bin/mysqld(_Z21mysql_execute_commandP3THD+0x8f9f)[0x5ce35f]
/data/maria/bin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1e)[0x545fae]
/data/maria/bin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x8c)[0x54614c]
/data/maria/bin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x522)[0x549792]
/data/maria/bin/mysqld(_ZN7sp_head7executeEP3THDb+0x622)[0x54b622]
/data/maria/bin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x623)[0x54cf63]
/data/maria/bin/mysqld(_Z21mysql_execute_commandP3THD+0x268f)[0x5c7a4f]
/data/maria/bin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1e)[0x545fae]
/data/maria/bin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x8c)[0x54614c]
/data/maria/bin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x522)[0x549792]
/data/maria/bin/mysqld(_ZN7sp_head7executeEP3THDb+0x622)[0x54b622]
/data/maria/bin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x623)[0x54cf63]
/data/maria/bin/mysqld(_ZN14Event_job_data7executeEP3THDb+0x7f2)[0x68f762]
/data/maria/bin/mysqld(_ZN19Event_worker_thread3runEP3THDP28Event_queue_element_for_exec+0x116)[0x8f6d86]
/data/maria/bin/mysqld(event_worker_thread+0x51)[0x8f6e21]
pthread_create.c:0(start_thread)[0x7fcad944aaa1]
/lib64/libc.so.6(clone+0x6d)[0x7fcad83c9bcd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fc87f988120): is an invalid pointer
Connection ID (thread ID): 8943247
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=off

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.

We think the query pointer is invalid, but we will try to print it anyway.
Query: INSERT IGNORE INTO hist.TB_OPR_QR_LOG
SELECT *
FROM spb.TB_OPR_QR_LOG
WHERE REG_DTTM BETWEEN SUBDATE(CURDATE(), NAME_CONST('i',1)) AND SUBDATE(CURDATE(), NAME_CONST('i',1)-1)

220102 00:31:18 mysqld_safe Number of processes running now: 0
220102 00:31:18 mysqld_safe mysqld restarted
2022-01-02 0:31:18 140376880588640 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2022-01-02 0:31:18 140376880588640 [Note] /data/maria/bin/mysqld (mysqld 10.1.44-MariaDB) starting as process 24491 ...
2022-01-02 0:31:18 140376880588640 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-01-02 0:31:18 140376880588640 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-02 0:31:18 140376880588640 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-02 0:31:18 140376880588640 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2022-01-02 0:31:18 140376880588640 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-02 0:31:18 140376880588640 [Note] InnoDB: Using Linux native AIO
2022-01-02 0:31:18 140376880588640 [Note] InnoDB: Using SSE crc32 instructions
2022-01-02 0:31:18 140376880588640 [Note] InnoDB: Initializing buffer pool, size = 8.0G
2022-01-02 0:31:19 140376880588640 [Note] InnoDB: Completed initialization of buffer pool
2022-01-02 0:31:19 140376880588640 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-02 0:31:19 140376880588640 [Note] InnoDB: Starting crash recovery from checkpoint LSN=10922249540635
2022-01-02 0:31:29 140376880588640 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 147693 row operations to undo
InnoDB: Trx id counter is 59342962176
2022-01-02 0:31:33 140376880588640 [Note] InnoDB: Starting final batch to recover 110439 pages from redo log
2022-01-02 0:31:34 140366957205248 [Note] InnoDB: To recover: 103955 pages from log
220102 0:31:36 [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.1.44-MariaDB
key_buffer_size=33554432
read_buffer_size=1048576
max_used_connections=0
max_threads=2002
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4174416 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x100000
/data/maria/bin/mysqld(my_print_stacktrace+0x2e)[0xc28c5e]
/data/maria/bin/mysqld(handle_fatal_signal+0x4bf)[0x78a5ff]
/lib64/libpthread.so.0(+0xf7e0)[0x7fac09d877e0]
220102 00:31:40 mysqld_safe mysqld from pid file /data/mariadata/spbMariaDBmha4.localdomain.pid ended
220102 00:36:20 mysqld_safe Starting mysqld daemon with databases from /data/mariadata
2022-01-02 0:36:20 140536696792928 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
2022-01-02 0:36:20 140536696792928 [Note] /data/maria/bin/mysqld (mysqld 10.1.44-MariaDB) starting as process 27280 ...
2022-01-02 0:36:20 140536696792928 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2022-01-02 0:36:20 140536696792928 [Note] InnoDB: The InnoDB memory heap is disabled
2022-01-02 0:36:20 140536696792928 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-01-02 0:36:20 140536696792928 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2022-01-02 0:36:20 140536696792928 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-02 0:36:20 140536696792928 [Note] InnoDB: Using Linux native AIO
2022-01-02 0:36:20 140536696792928 [Note] InnoDB: Using SSE crc32 instructions
2022-01-02 0:36:20 140536696792928 [Note] InnoDB: Initializing buffer pool, size = 8.0G
2022-01-02 0:36:21 140536696792928 [Note] InnoDB: Completed initialization of buffer pool
2022-01-02 0:36:22 140536696792928 [Note] InnoDB: Highest supported file format is Barracuda.
2022-01-02 0:36:22 140536696792928 [Note] InnoDB: Starting crash recovery from checkpoint LSN=10922249540635
2022-01-02 0:36:26 140536696792928 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 147693 row operations to undo
InnoDB: Trx id counter is 59342962176
2022-01-02 0:36:31 140536696792928 [Note] InnoDB: Starting final batch to recover 110439 pages from redo log
220102 0:36:34 [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.1.44-MariaDB
key_buffer_size=33554432
read_buffer_size=1048576
max_used_connections=0
max_threads=2002
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4174416 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x100000
/data/maria/bin/mysqld(my_print_stacktrace+0x2e)[0xc28c5e]
/data/maria/bin/mysqld(handle_fatal_signal+0x4bf)[0x78a5ff]
2022-01-02 0:36:36 140526772770560 [Note] InnoDB: To recover: 20078 pages from log
/lib64/libpthread.so.0(+0xf7e0)[0x7fd13fa237e0]
220102 00:36:37 mysqld_safe mysqld from pid file /data/mariadata/spbMariaDBmha4.localdomain.pid ended
=============================================================
INSERT IGNORE INTO hist.TB_OPR_QR_LOG
SELECT *
FROM spb.TB_OPR_QR_LOG
WHERE REG_DTTM BETWEEN SUBDATE(CURDATE(), NAME_CONST('i',1)) AND SUBDATE(CURDATE(), NAME_CONST('i',1)-1)

위와 같은 쿼리로 인해 signal 6가 발생하여 shutdown 되었고 재기동을 했으나 signal 11이 계속 발생하면서 재기동이 안되었습니다.
innodb_force_recovery를 1부터 4까지 설정한 뒤 재기동 해봤지만 역시 안되었고요..

그래서 백업한 걸로 복구 하기는 했는데..어떤 원인으로 signal 6가 발생한건지 알 수 있을까요?