Description:
J:\DB\mysql5717>bin\mysqld --console --port=3317
2017-04-06T20:47:36.191537Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see doc
umentation for more details).
2017-04-06T20:47:36.191537Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2017-04-06T20:47:36.191537Z 0 [Note] bin\mysqld (mysqld 5.7.17) starting as process 10792 ...
2017-04-06T20:47:36.207137Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-04-06T20:47:36.207137Z 0 [Note] InnoDB: Uses event mutexes
2017-04-06T20:47:36.207137Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-04-06T20:47:36.207137Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-04-06T20:47:36.207137Z 0 [Note] InnoDB: Number of pools: 1
2017-04-06T20:47:36.207137Z 0 [Note] InnoDB: Not using CPU crc32 instructions
2017-04-06T20:47:36.222737Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2017-04-06T20:47:36.222737Z 0 [Note] InnoDB: Completed initialization of buffer pool
2017-04-06T20:47:36.378739Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2017-04-06T20:47:36.378739Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 143468164900
2017-04-06T20:47:36.378739Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 143468164957
2017-04-06T20:47:36.378739Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 143468164957
2017-04-06T20:47:36.378739Z 0 [Note] InnoDB: Database was not shutdown normally!
2017-04-06T20:47:36.378739Z 0 [Note] InnoDB: Starting crash recovery.
2017-04-06T20:47:36.550342Z 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 19 row operations to undo
2017-04-06T20:47:36.550342Z 0 [Note] InnoDB: Trx id counter is 729088
2017-04-06T20:47:36.550342Z 0 [Note] InnoDB: Last MySQL binlog file position 0 584688072, file name mysql-bin.000085
2017-04-06T20:47:36.784345Z 0 [Note] InnoDB: Starting in background the rollback of uncommitted transactions
2017-04-06T20:47:36.784345Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2017-04-06T20:47:36.784345Z 0 [Note] InnoDB: Rolling back trx with id 718997, 19 rows to undo
2017-04-06T20:47:36.784345Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2017-04-06T20:47:36.784345Z 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2017-04-06 17:47:36 0x2028 InnoDB: Assertion failure in thread 8232 in file rem0rec.cc line 578
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.
20:47:36 UTC - mysqld got exception 0x80000003 ;
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=402653184
read_buffer_size=2097152
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1013547 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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...
2017-04-06T20:47:36.877946Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB.
14053fde2 mysqld.exe!my_sigabrt_handler()[my_thr_init.c:449]
1408e9fc9 mysqld.exe!raise()[winsig.c:587]
1408e8ec0 mysqld.exe!abort()[abort.c:82]
140650f78 mysqld.exe!ut_dbg_assertion_failed()[ut0dbg.cc:67]
140764e5b mysqld.exe!rec_get_offsets_func()[rem0rec.cc:579]
1407b58c6 mysqld.exe!page_cur_search_with_match_bytes()[page0cur.cc:793]
1406c3210 mysqld.exe!btr_cur_search_to_nth_level()[btr0cur.cc:1438]
14077dcab mysqld.exe!btr_pcur_open_low()[btr0pcur.ic:470]
14077fdef mysqld.exe!row_search_index_entry()[row0row.cc:1076]
1407ce031 mysqld.exe!row_undo_ins_remove_sec_low()[row0uins.cc:230]
1407cdd20 mysqld.exe!row_undo_ins_remove_sec()[row0uins.cc:296]
1407ce2bd mysqld.exe!row_undo_ins_remove_sec_rec()[row0uins.cc:424]
1407cd69d mysqld.exe!row_undo_ins()[row0uins.cc:478]
1407c2a7e mysqld.exe!row_undo()[row0undo.cc:326]
1407c2ec8 mysqld.exe!row_undo_step()[row0undo.cc:370]
1407766a9 mysqld.exe!que_thr_step()[que0que.cc:1054]
140775e1d mysqld.exe!que_run_threads_low()[que0que.cc:1121]
140775c12 mysqld.exe!que_run_threads()[que0que.cc:1160]
1406ad0f5 mysqld.exe!trx_rollback_active()[trx0roll.cc:680]
1406adc0a mysqld.exe!trx_rollback_resurrected()[trx0roll.cc:765]
1406ad7bb mysqld.exe!trx_rollback_or_clean_recovered()[trx0roll.cc:826]
1406ae98b mysqld.exe!trx_rollback_or_clean_all_recovered()[trx0roll.cc:872]
76fc59cd kernel32.dll!BaseThreadInitThunk()
770fa561 ntdll.dll!RtlUserThreadStart()
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.
2017-04-06T20:47:41.292802Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2017-04-06T20:47:41.292802Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
How to repeat:
constantly, I already drope the table and created again.... I already drop de tablespace and created again... and nothing.
when a specific table have millions of records, I means when a table have +-
more then 10 millions of records...
