Percona Server moved to https://jira.percona.com/projects/PS

FTS query exceeds result cache limit

Series 5.6
Bug #1542874

Bug #1542874 reported by monty solomon on 2016-02-07

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
MySQL Server	Unknown	Unknown	mysql-bugs #80296
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	Percona Server moved to https://jira.percona.com/projects/PS 5.7.14-7

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.

See original description

Tags:

Revision history for this message

monty solomon (monty+launchpad) wrote on 2016-02-07:

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;

description:

updated

Laurynas Biveinis (laurynas-biveinis) on 2016-02-08

tags:

added: innodb upstream

Revision history for this message

Yura Sorokin (yura-sorokin) wrote on 2016-08-08:

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).

Revision history for this message

Yura Sorokin (yura-sorokin) wrote on 2016-08-09:

https://github.com/percona/percona-server/pull/798