MySQL Bugs: #74769: innodb_fts.compatibility got Assertion in file ut0ut.cc line 905

Bug #74769	innodb_fts.compatibility got Assertion in file ut0ut.cc line 905
Submitted:	10 Nov 2014 15:09	Modified:	16 Dec 2014 19:12
Reporter:	Horst Hunger	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S2 (Serious)
Version:	5.7.6-0.3.m16	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
2014-11-08T18:40:46.890835Z 0 [ERROR] [FATAL] InnoDB: Setting parent table `test`.`t1`to hex format failed. Please try to restart the server again, if it doesn't work, the system tables might be corrupted.
2014-11-08 21:40:46 0x7fd122d9a740  InnoDB: Assertion failure in thread 140536209581888 in file ut0ut.cc line 905

Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(my_print_stacktrace+0x47)[0xf9f520]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(handle_fatal_signal+0x411)[0x8ed60a]
/lib64/libpthread.so.0(+0xf130)[0x7fd122995130]
/lib64/libc.so.6(gsignal+0x39)[0x7fd1215985c9]
/lib64/libc.so.6(abort+0x148)[0x7fd121599cd8]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug[0x122de13]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(_ZN2ib5fatalD1Ev+0x71)[0x1232bed]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug[0x1349015]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug[0x134a306]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(_Z24fts_drop_orphaned_tablesv+0x389)[0x134a79e]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(_Z29recv_recovery_rollback_activev+0x60)[0x10c62ca]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(_Z34innobase_start_or_create_for_mysqlv+0x27a1)[0x11d9a22]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug[0x103041d]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(_Z24ha_initialize_handlertonP13st_plugin_int+0x105)[0x94fee3]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug[0xcb6de0]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(_Z11plugin_initPiPPci+0x8b6)[0xcb79d4]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug[0x8dcb38]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(_Z11mysqld_mainiPPc+0x5c2)[0x8ddca8]
/export/home/pb2/test/sb_2-13632563-1415466136.23/usr/sbin/mysqld-debug(main+0x20)[0x8d5960]
/

See also Bug #19773353.

More info http://pb2.no.oracle.com/?action=archive_download&archive_id=13634740&pretty=please

How to repeat:
Test runs in PB2

Posted by developer:
 
commit 4511e1f646140afd9f5c540331bda3d0e2506601
Author: Thiru <thirunarayanan.balathandayuth@oracle.com>
Date:   Mon Dec 15 11:46:30 2014 +0530

    Bug #20001827       INNODB_FTS.COMPATIBILITY FAILING ASSERTION:
                !(TABLE->FLAGS2 & (64))
    
    Description:
    While renaming the windows fts file name to non windows file name,
    there is possibility of auxiliary table storing it twice.
    
    Solution:
    Before adding to auxiliary table to be renamed, check whether fts auxiliary
    table already exist.
    
        Approved by Jimmy (rb-7388)

Posted by developer:
 
Fixed as of the upcoming 5.7.6 release, and here's the changelog entry:

On Windows, renaming a "FULLTEXT" search file name raised an assertion.