processlist_with_stucked_query.txt
table_definition.txt
[MDEV-29177] After upgrade 10.4 -> 10.5 some UPDATE queries getting stuck in "init for update" state Created: 2022-07-27 Updated: 2023-01-20 Resolved: 2023-01-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Optimizer |
| Affects Version/s: | 10.5.15, 10.5.16 |
| Fix Version/s: | 10.5.17 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Jozef Kováč | Assignee: | Sergei Petrunia |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
RHEL 8.6 |
||
| Attachments: |
processlist_with_stucked_query.txt
table_definition.txt
|
| Description |
|
After upgrade mariadb server from 10.4.25 to 10.5.16 similar UPDATE queries stuck in "init for update" state for 2-60 minutes, same queries was and are executed under 10.4.25 in milliseconds. SHOW FULL PROCESSLIST added to attachment, it was during replication but same happen when query is executed manually. And also SHOW CREATE TABLE\G added. |
| Comments |
| Comment by Jozef Kováč [ 2022-07-28 ] |
|
It stuck in "init for update" state using Aria engine too but only for 10 seconds same query on InnoDB stuck for 3000s (killed after 600s) Tested 10+ times always 10s in "init for update" state. Setting optimizer_max_sel_arg_weight=320 with InnoDB/Aria query is executed very fast. 3200 produce short stuck in "init for update" state. |
| Comment by Jozef Kováč [ 2022-08-31 ] |
|
Can`t reproduce in 10.5.17. |
| Comment by Sergei Golubchik [ 2023-01-20 ] |
|
Thanks. I'll close it then, but please comment if it'll show up again |