抱歉,我的英语不流利。我是MySQL数据库的新手。我在 Windows Server 2022 Datacenter 上使用 MySQL 8.0.30。我有一个问题,MySQL 经常崩溃(MySQL 服务停止),并且总是带有相同的错误日志。我试图找到问题的根源,但没有解决。
有关信息,我在具有以下规格的同一设备上使用了 Grafana Web Server 和 MySQL: 处理器 Intel(R) Xeon(R) Silver 4208 CPU @ 2.10GHz 2.10 GHz 已安装 RAM 16.0 GB(15.6 GB 可用) 系统类型 64位操作系统,基于x64的处理器
请给我建议来解决这个问题。 先谢谢了
这是错误 MySQL 日志详细信息:
10:01:25 UTC - mysqld got exception 0xc0000005 ; 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... 7ffa8ac5b496 jemalloc.dll!??? 7ffa8ac5b918 jemalloc.dll!??? 7ffa8ac5ef91 jemalloc.dll!je_realloc() 7ffa82547ddd libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffa8258bcea libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffa8258e7e3 libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffa8255956d libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffa8246263c libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffa826092ff libcrypto-1_1-x64.dll!CRYPTO_memcmp() 7ffab7d47167 ntdll.dll!RtlActivateActivationContextUnsafeFast() 7ffab7d4848a ntdll.dll!LdrShutdownThread() 7ffab7d28bae ntdll.dll!RtlExitUserThread() 7ffab5851b8a KERNELBASE.dll!FreeLibraryAndExitThread() 7ffab55c6c5d ucrtbase.dll!_recalloc() 7ffab55f3c19 ucrtbase.dll!_endthreadex() 7ff682fc4605 mysqld.exe!?modify_thread_cache_size@Per_thread_connection_handler@@SAXK@Z() 7ff6844987a9 mysqld.exe!?deallocate@?$allocator@V?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@std@@@std@@QEAAXQEAV?$sub_match@V?$_String_const_iterator@V?$_String_val@U?$_Simple_types@D@std@@@std@@@std@@@2@_K@Z() [truncated, 260 bytes total] 7ff68405139c mysqld.exe!?my_thread_self_setname@@YAXPEBD@Z() 7ffab55c6b4c ucrtbase.dll!_recalloc() 7ffab7274ed0 KERNEL32.DLL!BaseThreadInitThunk() 7ffab7d9e44b 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.
我尝试减少数据读写,然后增加客户端连接限制
每秒速率 = RPS
为您的 my.ini [mysqld] 部分考虑的建议,以避免意外关闭。
**** 这是当前名称,而不是已弃用的每个错误日志的 innodb_log_file_size
请查看个人资料以获取联系信息。您有很多机会通过额外的全局变量更改来提高性能。
想听听您如何在 96 秒的正常运行时间内获得如此多的活动的故事。 :)