数据导入引发slave实例异常crash的bug定位与修复

文章目录

DB最近在搞迁移的事情，逻辑迁移过程中发现将数据从A集群迁移到B集群时，偶发B集群slave实例的crash。

整个问题的处理过程

1. 查看故障表象
2. 故障复现
3. 直接问题分析
4. 真正的问题定位
5. 问题修复

故障表象

错误日志中记录了crash时的线程堆栈信息，如下：

As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=33554432
read_buffer_size=16777216
max_used_connections=3
max_threads=5000
thread_count=6
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 122979486 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7ff6b414d9a0
Attempting backtrace. You ca