I have a big dumps (>55GB), which I regularly import into my local database.
Recently I upgraded XAMPP to 7.2.34 and the import couldn't be done. My previous version was 7.1.33 and everything was normal.
Usually I export the db with
- Code: Select all
mysqldump -u root -p xxx --single-transaction db_name > dump.sql
the import is
- Code: Select all
mysql -u root -p xxx db_name < dump.sql
OS 64bit Windows 10, 16GB RAM, AMD Ryzen 5 2400G with Radeon Vega Graphics 3.60 GHz, plenty of disk space.
- Code: Select all
InnoDB: ###### Diagnostic info printed to the standard error stream
2021-03-02 16:40:04 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
210302 16:40:04 [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.4.17-MariaDB-log
key_buffer_size=402653184
read_buffer_size=2097152
max_used_connections=5
max_threads=65537
thread_count=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 400450 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()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
mysqld.exe!??$_Construct_in_place@PEADAEBQEAD@std@@YAXAEAPEADAEBQEAD@Z()
mysqld.exe!pthread_dummy()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
And a lot of debugging information above this.
I split my db export to single tables. The biggest was ~ 14 GB text files. The import failed again.
I saw a similar thread at Zabbix forum: https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/416036-mysql-error-fatal-innodb-semaphore-wait-has-lasted-600-seconds
I downloaded previous version - 7.2.33 and extracted only mysql folder into my current setup.
Now it works and imports without problem, so I think 10.4.17-MariaDB-log is faulty.