[MDEV-12257] Slow queries with a query time of 601 seconds Created: 2017-03-14 Updated: 2017-05-15 Resolved: 2017-05-15 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.1.21 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Markus Nägele | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | need_feedback | ||
| Environment: |
CentOS release 6.8 (Final) amd64 on PowerEdge R510 |
||
| Attachments: |
|
| Description |
|
Since we upgraded from version 10.0.16 to 10.1.21 at the end of January we're finding a certain statement several times a day in the slow query log. The entry always looks like:
The create statements of the involved tables state and jobhead are attached. The table state is quite large, it has about 180 million rows (size on disk about 75G). This statement is executed hundreds of thousands times a day and only differs in the wanted values for colACCN and timestamp ('240118' and '2017-03-14 15:02:50' in the example above). While running MariaDB 10.0.16 we found it rarely in the slow query log (maybe once a week) with much lower query times (about 10 - 30 seconds). Since we switched to version 10.1.21 we find it in the slow query log 5 - 15 times a day and always with a query time of 601.xxxxxx seconds. Usually the statement needs some milliseconds to finish. We noticed the variable innodb_fatal_semaphore_wait_threshold with a default value of 600 seconds an wonder if it is related with the issue. Do you have any ideas what might cause this? How could we do a deeper analysis of this issue? I attached the values of all variables as well. If any further information is helpful, please let me know. |
| Comments |
| Comment by Elena Stepanova [ 2017-04-17 ] |
|
It is unlikely that innodb_fatal_semaphore_wait_threshold plays a role here, because that's when InnoDB is supposed to die, along with the server. Still, everything is possible, what does the error log say? If there is a long semaphore wait, there should be InnoDB status output there. Or, maybe there are other errors or warnings around the time when the problem occurs? |