[MDEV-10777] Server crashed due to query_cache_info plugin Created: 2016-09-09 Updated: 2016-09-27 Resolved: 2016-09-27 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Plugins, Query Cache |
| Affects Version/s: | 10.1.16 |
| Fix Version/s: | 10.1.18 |
| Type: | Bug | Priority: | Major |
| Reporter: | Valerii Kravchuk | Assignee: | Oleksandr Byelkin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | plugins | ||
| Sprint: | 10.2.2-4, 10.1.18 |
| Description |
|
MariaDB 10.1.16 server crashed after running for 1 hour with the query_cache_info plugin enabled:
with the following related settings:
and query cache related status typically looking like this:
Stack trace is the following:
and crashing query was:
|
| Comments |
| Comment by Oleksandr Byelkin [ 2016-09-14 ] |
|
revision-id: 325a9c760c9b13a9748a0cee27a98455b558df30 (mariadb-10.1.17-11-g325a9c7)
Possible fix. Make the pluging more safe. — |
| Comment by Oleksandr Byelkin [ 2016-09-16 ] |
|
revision-id: 1665680172edf8799ac5668487e09f1f4a1144c7 (mariadb-10.1.17-11-g1665680)
Possible fix. Make the pluging more safe. — |
| Comment by Vladislav Vaintroub [ 2016-09-23 ] |
|
sanja: I looked at the patch, I understand the logic, and the patch could work, if the issue on hand is related to underlocking in the plugin. Yet, I'm still left to guess why it is necessary to have a new "ready" flag instead of using an already existing and extensively used rw lock when looking at query result chain. |