FTS query exceeds result cache limit

Bug #1542874 reported by monty solomon on 2016-02-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Invalid
Undecided
Unassigned
5.6
New
Undecided
Unassigned
5.7
Fix Released
High
Unassigned

Bug Description

InnoDB full-text queries fail with error "ERROR 188 (HY000): FTS query exceeds result cache limit" using the maximum values of innodb_ft_result_cache_limit and innodb_ft_total_cache_size.

The failing queries executed properly when the engine was MyISAM.

mysql Ver 14.14 Distrib 5.6.25-73.1, for Linux (x86_64) using 6.0
Server version: 5.6.25-73.1-log Percona Server (GPL), Release 73.1, Revision 07b797f

CentOS release 6.7 (Final)

I created upstream bug http://bugs.mysql.com/bug.php?id=80296.

monty solomon (monty+launchpad) wrote :

Convert a large MyISAM FTS table to InnoDB. Execute queries that work with the MyISAM table on the InnoDB table.

Get error message
ERROR 188 (HY000): FTS query exceeds result cache limit

ALTER TABLE eventDetails ENGINE = InnoDB ROW_FORMAT=COMPRESSED KEY_BLOCK_SIZE=8;

mysql> show global variables like 'innodb_ft%';
+---------------------------------+------------+
| Variable_name | Value |
+---------------------------------+------------+
| innodb_ft_aux_table | |
| innodb_ft_cache_size | 8000000 |
| innodb_ft_enable_diag_print | OFF |
| innodb_ft_enable_stopword | ON |
| innodb_ft_max_token_size | 10 |
| innodb_ft_min_token_size | 4 |
| innodb_ft_num_word_optimize | 2000 |
| innodb_ft_result_cache_limit | 4294967295 |
| innodb_ft_server_stopword_table | |
| innodb_ft_sort_pll_degree | 2 |
| innodb_ft_total_cache_size | 1600000000 |
| innodb_ft_user_stopword_table | |
+---------------------------------+------------+
12 rows in set (0.25 sec)

description: updated
tags: added: innodb upstream
Yura Sorokin (yura-sorokin) wrote :

Fixed by Oracle in 5.7.14

From the release notes:
* InnoDB: A full-text query that involved a large number of records exceeded the result cache limit and caused a server exit. (Bug #22709692, Bug #80296).

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-965

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.