Bug #70226 FTS: InnoDB: Trying to TRUNCATE a missing index of table
Submitted: 3 Sep 2013 14:23 Modified: 24 Oct 2013 19:29
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S3 (Non-critical)
Version:5.6.13 OS:Any
Assigned to: CPU Architecture:Any

[3 Sep 2013 14:23] Shane Bester
Description:
Error log prints out this information:

InnoDB: Trying to TRUNCATE a missing index of table test/t1!
InnoDB: Trying to TRUNCATE a missing index of table test/t1!
InnoDB: Trying to TRUNCATE a missing index of table test/t1!
InnoDB: Trying to TRUNCATE a missing index of table test/t1!

How to repeat:
set global innodb_file_per_table=0;
drop table if exists t1;
create table t1(a char(10) charset latin1,fulltext(a))engine=innodb;
truncate t1;truncate t1;
truncate t1;truncate t1;

Suggested fix:
Do not spam the error log needlessly.

A previous case has been fixed by the fix for:
Bug 12429565 - FTS: INDEX IS MISSING FROM THE DATA DICTIONARY DURING TRUNCATE!
[24 Oct 2013 19:29] Daniel Price
Fixed as of 5.6.15, 5.7.3 and here's the changelog entry:

 During a "TRUNCATE TABLE" operation, "InnoDB: Trying to TRUNCATE a
missing index of table ..." warnings would be printed to the error log.
These warnings should not be printed when the index is an FTS index. 

Thank you for the bug report.
[4 Dec 2013 12:07] Laurynas Biveinis
5.6$ bzr log -r 5553
------------------------------------------------------------
revno: 5553
committer: Shaohua Wang <shaohua.wang@oracle.com>
branch nick: mysql-5.6-bugfix1
timestamp: Thu 2013-10-24 18:24:55 +0800
message:
  BUG#17402002 - FTS: INNODB: TRYING TO TRUNCATE A MISSING INDEX OF TABLE
  
  Supress the warning message when it's a fts index.
  
  rb#3683 approved by Jimmy.Yang