[MDEV-15631] [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. Created: 2018-03-22 Updated: 2021-12-23 Resolved: 2021-12-23 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.2.13, 10.3.5 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Sebastian Stamm | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows Server 2012 R2 , 256GB RAM |
||
| Attachments: |
|
| Description |
|
After mass/bulk insert the DB crashes with the following error:
|
| Comments |
| Comment by Sebastian Stamm [ 2018-04-02 ] |
|
With 10.2.13 i run into similar problems. With 10.2.14 seems like it's fixed, maybe related to: |
| Comment by Marko Mäkelä [ 2018-04-07 ] |
|
sstamm, can you please provide more information, such as stack traces from the server during the 10-minute hang before the InnoDB watchdog finally killed the server? On Windows, procmon should be useful. One known cause of a watchdog kill is reported in Could this be caused by the InnoDB change buffer? Can you repeat with innodb_change_buffering=none? |
| Comment by Vladislav Vaintroub [ 2018-04-07 ] |
|
marko meant procdump from https://docs.microsoft.com/en-us/sysinternals/downloads/procdump. "procdump mysqld.exe" would generate a dump. If you could supply that dump, this would be great. The issue I'm working on is |
| Comment by Sebastian Stamm [ 2018-04-10 ] |
|
Unfortunately I'm not able to reproduce it at short (switched to 10.2.14). |
| Comment by Marko Mäkelä [ 2018-04-15 ] |
|
sstamm, could this be a duplicate of |