抱歉,我的英文不流利。我是MySQL資料庫(kù)的新手。我在 Windows Server 2022 Datacenter 上使用 MySQL 8.0.30。我有一個(gè)問(wèn)題,MySQL 經(jīng)常崩潰(MySQL 服務(wù)停止),並且總是帶有相同的錯(cuò)誤日誌。我試著找出問(wèn)題的根源,但沒(méi)有解決。
有關(guān)信息,我在具有以下規(guī)格的同一設(shè)備上使用了 Grafana Web Server 和 MySQL: 處理器 Intel(R) Xeon(R) Silver 4208 CPU @ 2.10GHz 2.10 GHz 已安裝 RAM 16.0 GB(15.6 GB 可用) 系統(tǒng)類型 64位元作業(yè)系統(tǒng),基於x64的處理器
請(qǐng)給我建議來(lái)解決這個(gè)問(wèn)題。 先謝謝了
這是錯(cuò)誤 MySQL 日誌詳細(xì)資訊:
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.
我嘗試減少資料讀寫(xiě),然後增加客戶端連線限制
每秒速率 = RPS
為您的 my.ini [mysqld] 部分考慮的建議,以避免意外關(guān)閉。
innodb_thread_concurrency=10 # from 33 for reasonable limit for your 16 available total threads innodb_redo_log_capacity=96M # from innodb_log_file_size name and 48M limit
**** 這是目前名稱,而不是已棄用的每個(gè)錯(cuò)誤日誌的 innodb_log_file_size
innodb_buffer_pool_size=8G # from 124M for about 1/2 available RAM to reduce innodb_data_reads RPS of 31. read_rnd_buffer_size=32K from 256K to reduce handler_read_rnd_next RPS of 63,041 thread_cache_size=128 # from 10 to reduce threads_created RPS of ~ 5
請(qǐng)查看個(gè)人資料以取得聯(lián)絡(luò)資訊。您有很多機(jī)會(huì)透過(guò)額外的全域變數(shù)變更來(lái)提高效能。
想聽(tīng)聽(tīng)您如何在 96 秒的正常運(yùn)行時(shí)間內(nèi)獲得如此多的活動(dòng)的故事。 :)