MySQL Bugs: #84975: Assertion failure in thread 139870064981760 in file trx0trx.cc line 1465

Bug #84975	Assertion failure in thread 139870064981760 in file trx0trx.cc line 1465
Submitted:	14 Feb 2017 7:07	Modified:	1 Apr 2017 14:35
Reporter:	Masanao KITORA	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.7.17	OS:	CentOS
Assigned to:		CPU Architecture:	Any

Description:
Below logs are written down to mysqld.log.
I don't know this happens with which operation.

Around 12hours later of this message mysqld process crashed.
I had to set 'innodb_force_recovery=1' option to restart mysqld.

-----
2017-02-13T15:03:57.757294Z 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 6527ms. The settings might not be optimal. (flushed=200 and evicted=0, during
the time.)
2017-02-13T15:05:44.132695Z 33115 [Warning] InnoDB: Cannot create table `cts`.`FTS_0000000000000142_0000000000000279_INDEX_6` because tablespace full
2017-02-13T15:05:44.132750Z 33115 [Warning] InnoDB: Failed to create FTS index table cts/FTS_0000000000000142_0000000000000279_INDEX_6
2017-02-14 00:05:44 0x7f360989b700  InnoDB: Assertion failure in thread 139870064981760 in file trx0trx.cc line 1465
InnoDB: Failing assertion: trx->error_state == DB_SUCCESS
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.
15:05:44 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=39
max_threads=128
thread_count=20
connection_count=20
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2123436 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f374c751920
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 = 7f360989ae28 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0xf42a95]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x7cd8b4]
/lib64/libpthread.so.0[0x30bf00f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x30bec325e5]
/lib64/libc.so.6(abort+0x175)[0x30bec33dc5]
/usr/sbin/mysqld(_Z18ut_print_timestampP8_IO_FILE+0x0)[0x7bcb4e]
/usr/sbin/mysqld[0x1179b98]
/usr/sbin/mysqld(_Z24row_drop_table_for_mysqlPKcP5trx_tbbP12dict_table_t+0x8c5)[0x10faa45]
/usr/sbin/mysqld(_Z27fts_create_index_tables_lowP5trx_tPK12dict_index_tPKcm+0x339)[0x1260f59]
/usr/sbin/mysqld(_Z26row_create_index_for_mysqlP12dict_index_tP5trx_tPKmP12dict_table_t+0x475)[0x10fd455]
/usr/sbin/mysqld(_Z12create_indexP5trx_tPK5TABLEmPKcj+0x73b)[0x1038d2b]
/usr/sbin/mysqld(_ZN19create_table_info_t12create_tableEv+0xd9)[0x10235d9]
/usr/sbin/mysqld(_ZN11ha_innobase6createEPKcP5TABLEP24st_ha_create_information+0x116)[0x1023f16]
/usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationbb+0x2c3)[0x818893]
/usr/sbin/mysqld(_Z17mysql_alter_tableP3THDPKcS2_P24st_ha_create_informationP10TABLE_LISTP10Alter_info+0x2f13)[0xd79873]
/usr/sbin/mysqld(_ZN19Sql_cmd_alter_table7executeEP3THD+0x501)[0xe82241]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THDb+0x17e2)[0xd0b062]
/usr/sbin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3a5)[0xd0ed95]
/usr/sbin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0x1778)[0xd10578]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x194)[0xd10ea4]
/usr/sbin/mysqld(handle_connection+0x29c)[0xde3f1c]
/usr/sbin/mysqld(pfs_spawn_thread+0x174)[0xf60b74]
/lib64/libpthread.so.0[0x30bf007aa1]
/lib64/libc.so.6(clone+0x6d)[0x30bece8aad]

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

The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
Don't know

Hi,

Thank you for your bug report. This appears to be an error due to the configuration or due to your hardware limitations.

For the moment, I have two questions:

* When creating a tablespace, have you made it auto-extendable ???

* Is there enough space on the disk partition where it is residing ???

After you answer these questions, we can move on ...

One more important question:

Are you using innodb-file-per-table=NO ??? Or is this option set to YES ???

If it is NO, then the FTS indexes may be in the system tablesapce ...

And only the system tablespace, and temp tablespace, can be a fixed size. If that is the case than this is not a bug, but mis-configuration of your installation.

In my.cnf below settings exist, 
innodb_data_file_path=ibdata1:1G
innodb_file_per_table

Shared table space is not auto-extendable.
Each innodb table has idb file.
It seems FTS_...  files are created out of shared table space.

Yes, they are. If you have not configured InnoDB to use one file for each table, then it is what you get. Just as I described in my previous comments.

>* When creating a tablespace, have you made it auto-extendable ???

-> No. I prepared 1GB fixed table space.

>* Is there enough space on the disk partition where it is residing ???

-> Yes. 5TB- available for /var/lib/mysql.

>*Are you using innodb-file-per-table=NO ??? Or is this option set to YES ???

-> I'm using innodb-file-per-table=YES.

I think my environment resources are
 1GB for shared space
 upto 5TB for each table space.

Hi!

It is quite possible that you created that table with FTS before you have set innodb-file-per-table=YES ???

In any case, do you see that table as a separate file. If yes, send us a listing of that directory, together with your my.cnf

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".