MySQL8.0.28数据库在windows版本下运行宕机问题解决

问题描述

MySQL8.0.28数据库在windows2022服务器上运行，使用Navicat执行数据备份或者是在并发量较高的情况下会自行宕机，查看日志后发现报错问题如下：

mysqld got exception 0x16 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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...
7ff6753cfd48    mysqld.exe!my_print_stacktrace()[stacktrace.cc:429]
7ff67460004b    mysqld.exe!print_fatal_signal()[signal_handler.cc:130]
7ff6745ffe13    mysqld.exe!my_server_abort()[signal_handler.cc:241]
7ff6753b643a    mysqld.exe!my_abort()[my_init.cc:263]
7ff6755ec579    mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:99]
7ff67553bd51    mysqld.exe!SyncFileIO::execute()[os0file.cc:3776]
7ff67553d5da    mysqld.exe!os_aio_windows_handler()[os0file.cc:7188]
7ff67553c7da    mysqld.exe!os_aio_handler()[os0file.cc:6120]
7ff67555e3f4    mysqld.exe!fil_aio_wait()[fil0fil.cc:8207]
7ff6755ae091    mysqld.exe!io_handler_thread()[srv0start.cc:281]
7ff6755ab7b4    mysqld.exe!std::thread::_Invoke<std::tuple<Detached_thread,void (__cdecl*)(unsigned __int64),unsigned __int64>,0,1,2>()[thread:54]
7ffea5cc6b4c    ucrtbase.dll!_recalloc()
7ffea78b4de0    KERNEL32.DLL!BaseThreadInitThunk()
7ffea801ec4b    ntdll.dll!RtlUserThreadStart()
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.

问题解决

简单来说就是8.0.28本身数据库的bug，在8.0.29版本已经修复，建议使用8.0.34版本

官方社区相关问题：
https://forums.mysql.com/read.php?22,703528,703529

解决：

It was fixed in the 8.0.29 release, with the following bugs:
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-29.html

- InnoDB: The AIO synchronization queue used on Windows was removed. The synchronous file I/O read-write function (SyncFileIO::execute) was revised to handle files opened for both normal and overlapped I/O, as it does on Linux. (Bug #33840645)

- InnoDB: A thread posted an asynchronous I/O operation and closed itself, resulting in an operating system file operation error. (Bug #30567295)

The 995 error is not an fatal error in itself, but it was handled incorrectly, leading to a crash. Currently it should only be reported on INFO level and can be safely ignored.