Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.13, 10.3.5
-
None
-
Windows Server 2012 R2 , 256GB RAM
Description
After mass/bulk insert the DB crashes with the following error:
2018-03-20 17:44:36 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
|
180320 17:44:36 [ERROR] mysqld got exception 0x80000003 ;
|
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.3.5-MariaDB
|
key_buffer_size=134217728
|
read_buffer_size=67108864
|
max_used_connections=85
|
max_threads=65537
|
thread_count=90
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 264089 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...
|
mysqld.exe!my_parameter_handler()[my_init.c:260]
|
mysqld.exe!raise()[signal.cpp:516]
|
mysqld.exe!abort()[abort.cpp:71]
|
mysqld.exe!ib::fatal::~fatal()[ut0ut.cc:795]
|
mysqld.exe!srv_error_monitor_thread()[srv0srv.cc:1864]
|
KERNEL32.DLL!BaseThreadInitThunk()
|
ntdll.dll!RtlUserThreadStart()
|