[MDEV-24924] Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung. Created: 2021-02-19 Updated: 2021-03-28 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.5.7 |
| Fix Version/s: | 10.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Milad Elhaei Sahar | Assignee: | Marko Mäkelä |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | mariadb | ||
| Environment: |
Linux, cpu_cores : 4, memory total : 34G swap_total : 2G |
||
| Attachments: |
|
| Description |
|
We start seeing this mariadb crash log with this long semaphores wait. In this mariadb instance we have one database with couple of big tables with 250+ million rows. We read other jira tickets with semaphores error but seems ours is not exactly same so now we thinking to increase the number of max open files 16384 to something around 32000, but not sure if it will fix the issue or it is at all related to this mariadb crash. During this long semaphore wait we see higher cpu IO wait and increase in read requests from disk.
|
| Comments |
| Comment by Milad Elhaei Sahar [ 2021-02-19 ] | ||||||||||||||||||
|
do you think this bug will be fixed in the coming release? I see some jira tickets also report the same bug with 10.5.8. | ||||||||||||||||||
| Comment by Marko Mäkelä [ 2021-02-19 ] | ||||||||||||||||||
|
Please post the stack traces of all threads during the hang. This could be a duplicate of | ||||||||||||||||||
| Comment by Milad Elhaei Sahar [ 2021-02-19 ] | ||||||||||||||||||
|
Hi Marko
|