Bug #83844 mysql 5.7 fts bug
Submitted: 16 Nov 2016 13:41 Modified: 21 Nov 2016 6:58
Reporter: Gyuseub Shin Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: FULLTEXT search Severity:S1 (Critical)
Version:mysql 5.7.16 OS:CentOS
Assigned to: CPU Architecture:Any
Tags: fts

[16 Nov 2016 13:41] Gyuseub Shin
Description:
My log message is : 

2016-11-16 22:01:10 0x7fb20031c700  InnoDB: Assertion failure in thread 140402484168448 in file fts0que.cc line 3559
InnoDB: Failing assertion: ret == 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:01:10 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=321
max_threads=4000
thread_count=7
connection_count=7
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1597567 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fb1b40008c0
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 = 7fb20031be28 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0xf40b15]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x7cdf24]
/lib64/libpthread.so.0[0x3bedc0f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x3bed8325e5]
/lib64/libc.so.6(abort+0x175)[0x3bed833dc5]
/usr/sbin/mysqld(_Z18ut_print_timestampP8_IO_FILE+0x0)[0x7bccf4]
/usr/sbin/mysqld(_Z9fts_queryP5trx_tP12dict_index_tjPKhmPP12fts_result_ty+0xd93)[0x1216323]
/usr/sbin/mysqld(_ZN11ha_innobase11ft_init_extEjjP6String+0x16a)[0xfcc33a]
/usr/sbin/mysqld(_ZN15Item_func_match11init_searchEP3THD+0x141)[0x890b11]
/usr/sbin/mysqld(_Z12init_ftfuncsP3THDP13st_select_lex+0x4c)[0xcac31c]
/usr/sbin/mysqld(_ZN4JOIN8optimizeEv+0x2032)[0xd048c2]
/usr/sbin/mysqld(_ZN13st_select_lex8optimizeEP3THD+0x672)[0xd48352]
/usr/sbin/mysqld(_Z12handle_queryP3THDP3LEXP12Query_resultyy+0x21f)[0xd485ff]
/usr/sbin/mysqld[0xd09553]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x36f8)[0xd0cf18]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3ed)[0xd0eccd]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x111e)[0xd0fe4e]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x194)[0xd10ab4]
/usr/sbin/mysqld(handle_connection+0x29c)[0xde2e0c]
/usr/sbin/mysqld(pfs_spawn_thread+0x174)[0x1252bb4]
/lib64/libpthread.so.0[0x3bedc07aa1]
/lib64/libc.so.6(clone+0x6d)[0x3bed8e8aad]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fb1b4022600): is an invalid pointer
Connection ID (thread ID): 1497000
Status: NOT_KILLED

My my.cnf is :

# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
innodb_buffer_pool_size = 8G
innodb_log_file_size = 2G
innodb_buffer_pool_instances = 8
innodb_file_per_table = 1
innodb_flush_log_at_trx_commit = 2
innodb_log_buffer_size = 64M
innodb_lru_scan_depth = 100
innodb_page_cleaners = 8

#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.

datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

max_connections = 4000
ngram_token_size=2
sql_mode = NO_AUTO_CREATE_USER

log-error=/var/log/mysql/mysql.log
pid-file=/var/run/mysqld/mysqld.pid

slow_query_log = 1
slow_query_log_file     = /var/log/mysql/mysql-slow.log
long_query_time = 3

#key_buffer_size = 1G
max_allowed_packet = 16M
#table_open_cache = 2000
#sort_buffer_size = 1M
#read_buffer_size = 1M
#read_rnd_buffer_size = 16M
query_cache_size = 0
wait_timeout = 20
thread_cache_size = 64

explicit_defaults_for_timestamp = 1
skip_name_resolve = 1
optimizer_switch=derived_merge=off

Server is :

Centos 6.3
8 Core
16 GB

How to repeat:
I don't know.
[21 Nov 2016 6:58] MySQL Verification Team
Hello Gyuseub Shin,

Thank you for the report. Could you please provide exact repeatable test case(table structure, subset of data, and query which trigering this issue) to reproduce this issue at our end? If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thanks,
Umesh