[MDEV-16865] InnoDB fts_query() ignores KILL Created: 2018-07-31 Updated: 2018-08-03 Resolved: 2018-08-01 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB, Storage Engine - XtraDB |
| Affects Version/s: | 10.0, 10.1, 10.2, 10.3 |
| Fix Version/s: | 10.0.37, 10.1.36, 10.2.17, 10.3.9 |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | fulltext, kill | ||
| Issue Links: |
|
||||||||
| Description |
|
The functions fts_ast_visit() and fts_query() inside InnoDB FULLTEXT INDEX query processing are not checking for THD::killed (trx_is_interrupted()), like anything that potentially takes a long time should do. We should backport Bug #27155294 MAX_EXECUTION_TIME NOT INTERUPTED WITH FULLTEXT SEARCH USING MECAB PROBLEM from MySQL 5.7.23 to address this. |
| Comments |
| Comment by Marko Mäkelä [ 2018-08-03 ] |
|
The fix from upstream contained an error, which slipped into the 10.0.37 release, but will be fixed in MariaDB Server 10.0.38. A wrong pointer was tested for NULL in a clean-up code path, potentially leading to a SIGSEGV if a FULLTEXT INDEX query is killed (or the client disconnects before completion). |