问题表现
数据库不断自己重启，基本每分钟自己启动一次，应用无法连接 无法使用
报错日志
2021-02-08 09:55:16 0x7f0334fd7700 InnoDB: Assertion failure in thread 139651750655744 in file btr0cur.cc line 333
InnoDB: Failing assertion: btr_page_get_next( latch_leaves.blocks[0]->frame, mtr) == page_get_page_no(page)
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.
01:55:16 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=4194304
max_used_connections=439
max_threads=8000
thread_count=439
connection_count=439
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 65651254 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7efe3c000ae0
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 = 7f0334fd6e40 thread_stack 0x80000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2c)[0xf0a6ac]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x476)[0x7e9df6]
/lib64/libpthread.so.0(+0xf5d0)[0x7f38dfcc25d0]
/lib64/libc.so.6(gsignal+0x37)[0x7f38de6ab207]
/lib64/libc.so.6(abort+0x148)[0x7f38de6ac8f8]
/usr/local/mysql/bin/mysqld[0x7baa02]
/usr/local/mysql/bin/mysqld(_Z20btr_cur_latch_leavesP11buf_block_tRK9page_id_tRK11page_size_tmP9btr_cur_tP5mtr_t+0x8d8)[0x124a778]
/usr/local/mysql/bin/mysqld(_Z27btr_cur_search_to_nth_levelP12dict_index_tmPK8dtuple_t15page_cur_mode_tmP9btr_cur_tmPKcmP5mtr_t+0x1b4d)[0x1251c3d]
/usr/local/mysql/bin/mysqld(_Z27row_ins_sec_index_entry_lowmmP12dict_index_tP16mem_block_info_tS2_P8dtuple_tmP9que_thr_tb+0x2af)[0x116c51f]
/usr/local/mysql/bin/mysqld(_Z23row_ins_sec_index_entryP12dict_index_tP8dtuple_tP9que_thr_tb+0x2c7)[0x11712c7]
/usr/local/mysql/bin/mysqld(_Z12row_ins_stepP9que_thr_t+0x2c4)[0x1173544]
/usr/local/mysql/bin/mysqld[0x1184ede]
/usr/local/mysql/bin/mysqld(_ZN11ha_innobase9write_rowEPh+0x307)[0x10a9287]
/usr/local/mysql/bin/mysqld(_ZN7handler12ha_write_rowEPh+0x10a)[0x8417da]
/usr/local/mysql/bin/mysqld(_Z12write_recordP3THDP5TABLEP9COPY_INFOS4_+0xa3)[0xe534c3]
/usr/local/mysql/bin/mysqld(_ZN14Sql_cmd_insert12mysql_insertEP3THDP10TABLE_LIST+0x885)[0xe54765]
/usr/local/mysql/bin/mysqld(_ZN14Sql_cmd_insert7executeEP3THD+0xcb)[0xe54fab]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THDb+0x5b0)[0xcdacb0]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDP12Parser_state+0x3dd)[0xce10bd]
/usr/local/mysql/bin/mysqld(_Z16dispatch_commandP3THDPK8COM_DATA19enum_server_command+0xb3a)[0xce1caa]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0x177)[0xce36c7]
/usr/local/mysql/bin/mysqld(handle_connection+0x278)[0xda1f78]
/usr/local/mysql/bin/mysqld(pfs_spawn_thread+0x1b4)[0x13c9934]
/lib64/libpthread.so.0(+0x7dd5)[0x7f38dfcbadd5]
/lib64/libc.so.6(clone+0x6d)[0x7f38de772ead]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7efe3c005640): INSERT INTO I_USER_ORDER_280 (SUB_TYPE, SERV_ID, SERV_TYPE, SP_CODE, OPERATOR_CODE , THIRD_MSISDN, VALID_DATE, DONE_CODE, BUSI_TYPE, MSISDN , PROPERTY, REGION_CODE, ORDER_STS, CHANGE_TIME, EXPIRE_DATE , REMARK, SO_NBR, SRC_TYPE, EXTEND_FLAG, IS_NEW , HIS_FIRST_ORDER_TIME, FIRST_ORDER_TIME, LAST_ORDER_TIME, CHARGE_TYPE, SERVICE_TYPE , SO_ID, CHANNEL_CODE, DEVICE_SN, CSN_TIME, CAMPAIGN_ID , CAMPAIGN_RULES, SERIAL_NUMBER) VALUES ( xxx,xxxx)
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.
2021-02-08T01:55:44.225007Z mysqld_safe Number of processes running now: 0
2021-02-08T01:55:44.229262Z mysqld_safe mysqld restarted
2021-02-08T09:55:44.435428+08:00 0 [Warning] 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and 'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict mode. They will be merged with strict mode in a future release.
2021-02-08T09:55:44.435506+08:00 0 [Warning] 'NO_AUTO_CREATE_USER' sql mode was not set.
2021-02-08T09:55:44.437383+08:00 0 [Warning] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory.
2021-02-08T09:55:44.437430+08:00 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.7.32-log) starting as process 41495 ...
2021-02-08T09:55:44.442199+08:00 0 [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2021-02-08T09:55:44.442227+08:00 0 [Warning] InnoDB: Using innodb_file_format_max is deprecated and the parameter may be removed in future releases. See http://dev.mysql.com/doc/refman/5.7/en/innodb-file-format.html
2021-02-08T09:55:44.442290+08:00 0 [Note] InnoDB: PUNCH HOLE support available
2021-02-08T09:55:44.442302+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-02-08T09:55:44.442309+08:00 0 [Note] InnoDB: Uses event mutexes
2021-02-08T09:55:44.442315+08:00 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2021-02-08T09:55:44.442320+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-02-08T09:55:44.442325+08:00 0 [Note] InnoDB: Using Linux native AIO
2021-02-08T09:55:44.446426+08:00 0 [Note] InnoDB: Number of pools: 1
2021-02-08T09:55:44.446557+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2021-02-08T09:55:44.450149+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 200G, instances = 16, chunk size = 128M
2021-02-08T09:55:59.905540+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2021-02-08T09:56:02.893988+08:00 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-02-08T09:56:02.944582+08:00 0 [Note] InnoDB: Opened 8 undo tablespaces
2021-02-08T09:56:02.944615+08:00 0 [Note] InnoDB: 8 undo tablespaces made active
2021-02-08T09:56:02.944876+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2021-02-08T09:56:05.316049+08:00 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 4435067038321
2021-02-08T09:56:09.740585+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435072281088
2021-02-08T09:56:09.939103+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435077523968
2021-02-08T09:56:10.147822+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435082766848
2021-02-08T09:56:10.346682+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435088009728
2021-02-08T09:56:10.533734+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435093252608
2021-02-08T09:56:10.735096+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435098495488
2021-02-08T09:56:10.975319+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435103738368
2021-02-08T09:56:11.224462+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435108981248
2021-02-08T09:56:11.467459+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435114224128
2021-02-08T09:56:11.679546+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435119467008
2021-02-08T09:56:11.904581+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435124709888
2021-02-08T09:56:12.104743+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435129952768
2021-02-08T09:56:12.327404+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435135195648
2021-02-08T09:56:12.478000+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435140438528
2021-02-08T09:56:12.715202+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435145681408
2021-02-08T09:56:12.935373+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435150924288
2021-02-08T09:56:13.414564+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435156167168
2021-02-08T09:56:14.025977+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435161410048
2021-02-08T09:56:14.853008+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4435166246880
2021-02-08T09:56:14.855011+08:00 0 [Note] InnoDB: Database was not shutdown normally!
2021-02-08T09:56:14.855023+08:00 0 [Note] InnoDB: Starting crash recovery.
2021-02-08T09:56:18.209903+08:00 0 [Note] InnoDB: Transaction 41833873061 was in the XA prepared state.
2021-02-08T09:56:18.230145+08:00 0 [Note] InnoDB: 53 transaction(s) which must be rolled back or cleaned up in total 1194 row operations to undo
2021-02-08T09:56:18.230162+08:00 0 [Note] InnoDB: Trx id counter is 41833873408
2021-02-08T09:56:18.230180+08:00 0 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
2021-02-08T09:56:34.472380+08:00 0 [Note] InnoDB: Apply batch completed
2021-02-08T09:56:34.472441+08:00 0 [Note] InnoDB: Last MySQL binlog file position 0 93378540, file name mysql-bin.000329
2021-02-08T09:56:47.735881+08:00 0 [Note] InnoDB: Starting in background the rollback of uncommitted transactions
2021-02-08T09:56:47.735938+08:00 0 [Note] InnoDB: Rolling back trx with id 41833873040, 1 rows to undo
2021-02-08T09:56:47.735943+08:00 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2021-02-08T09:56:47.735976+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2021-02-08T09:56:47.736024+08:00 0 [Note] InnoDB: Setting file '/data/mysqldata/93306/data/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-02-08T09:56:47.740756+08:00 0 [Note] InnoDB: File '/data/mysqldata/93306/data/ibtmp1' size is now 12 MB.
2021-02-08T09:56:47.742000+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2021-02-08T09:56:47.742015+08:00 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2021-02-08T09:56:47.742375+08:00 0 [Note] InnoDB: Waiting for purge to start
2021-02-08T09:56:47.756790+08:00 0 [Note] InnoDB: Rollback of trx with id 41833873040 completed
2021-02-08T09:56:47.756817+08:00 0 [Note] InnoDB: Rolling back trx with id 41833873024, 2 rows to undo
2021-02-08T09:56:47.792460+08:00 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 44898ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)
2021-02-08T09:56:47.795429+08:00 0 [Note] InnoDB: Rollback of trx with id 41833873024 completed
2021-02-08T09:56:47.795455+08:00 0 [Note] InnoDB: Rolling back trx with id 41833872906, 3 rows to undo
2021-02-08T09:56:47.797121+08:00 0 [Note] InnoDB: 5.7.32 started; log sequence number 4435166246880
2021-02-08T09:56:47.797235+08:00 0 [Note] InnoDB: Loading buffer pool(s) from /data/mysqldata/93306/data/ib_buffer_pool
2021-02-08T09:56:47.797488+08:00 0 [Note] Plugin 'FEDERATED' is disabled.
2021-02-08T09:56:47.818770+08:00 0 [Note] Recovering after a crash using /data/mysqldata/93306/binlog/mysql-bin
2021-02-08T09:56:47.829742+08:00 0 [Note] InnoDB: Rollback of trx with id 41833872906 completed
2021-02-08T09:56:47.829769+08:00 0 [Note] InnoDB: Rolling back trx with id 41833872835, 3 rows to undo
2021-02-08T09:56:47.857073+08:00 0 [Note] InnoDB: Rollback of trx with id 41833872835 completed
2021-02-08T09:56:47.857108+08:00 0 [Note] InnoDB: Rolling back trx with id 41833872832, 3 rows to undo
2021-02-08T09:56:47.895304+08:00 0 [Note] InnoDB: Rollback of trx with id 41833872832 completed
2021-02-08T09:56:47.895332+08:00 0 [Note] InnoDB: Rolling back trx with id 41833872606, 3 rows to undo
2021-02-08T09:56:47.902802+08:00 0 [Note] InnoDB: Rollback of trx with id 41833872606 completed
2021-02-08T09:56:47.902826+08:00 0 [Note] InnoDB: Rolling back trx with id 41833872393, 2 rows to undo
2021-02-08T09:56:47.941285+08:00 0 [Note] InnoDB: Rollback of trx with id 41833872393 completed
2021-02-08T09:56:47.941306+08:00 0 [Note] InnoDB: Rolling back trx with id 41833872342, 3 rows to undo
2021-02-08T09:56:47.965739+08:00 0 [Note] InnoDB: Rollback of trx with id 41833872342 completed
2021-02-08T09:56:47.965763+08:00 0 [Note] InnoDB: Rolling back trx with id 41833872323, 3 rows to undo
2021-02-08T09:56:47.975712+08:00 0 [Note] InnoDB: Rollback of trx with id 41833872323 completed
2021-02-08T09:56:47.975735+08:00 0 [Note] InnoDB: Rolling back trx with id 41833871847, 3 rows to undo
2021-02-08T09:56:47.991858+08:00 0 [Note] InnoDB: Rollback of trx with id 41833871847 completed
2021-02-08T09:56:47.991880+08:00 0 [Note] InnoDB: Rolling back trx with id 41833871347, 9 rows to undo
2021-02-08T09:56:48.043402+08:00 0 [Note] InnoDB: Rollback of trx with id 41833871347 completed
2021-02-08T09:56:48.043428+08:00 0 [Note] InnoDB: Rolling back trx with id 41833870173, 12 rows to undo
2021-02-08T09:56:48.057968+08:00 0 [Note] InnoDB: Rollback of trx with id 41833870173 completed
2021-02-08T09:56:48.057995+08:00 0 [Note] InnoDB: Rolling back trx with id 41833870160, 15 rows to undo
2021-02-08T09:56:48.077654+08:00 0 [Note] InnoDB: Rollback of trx with id 41833870160 completed
2021-02-08T09:56:48.077676+08:00 0 [Note] InnoDB: Rolling back trx with id 41833870143, 9 rows to undo
2021-02-08T09:56:48.124445+08:00 0 [Note] InnoDB: Rollback of trx with id 41833870143 completed
2021-02-08T09:56:48.124466+08:00 0 [Note] InnoDB: Rolling back trx with id 41833870068, 3 rows to undo
2021-02-08T09:56:48.148137+08:00 0 [Note] InnoDB: Rollback of trx with id 41833870068 completed
2021-02-08T09:56:48.148159+08:00 0 [Note] InnoDB: Rolling back trx with id 41833869841, 9 rows to undo
2021-02-08T09:56:48.176242+08:00 0 [Note] InnoDB: Rollback of trx with id 41833869841 completed
2021-02-08T09:56:48.176260+08:00 0 [Note] InnoDB: Rolling back trx with id 41833869809, 9 rows to undo
2021-02-08T09:56:48.226485+08:00 0 [Note] InnoDB: Rollback of trx with id 41833869809 completed
2021-02-08T09:56:48.226504+08:00 0 [Note] InnoDB: Rolling back trx with id 41833869752, 3 rows to undo
2021-02-08T09:56:48.249408+08:00 0 [Note] InnoDB: Rollback of trx with id 41833869752 completed
2021-02-08T09:56:48.249428+08:00 0 [Note] InnoDB: Rolling back trx with id 41833869565, 18 rows to undo
2021-02-08T09:56:48.268344+08:00 0 [Note] InnoDB: Rollback of trx with id 41833869565 completed
2021-02-08T09:56:48.268368+08:00 0 [Note] InnoDB: Rolling back trx with id 41833868377, 6 rows to undo
2021-02-08T09:56:48.283542+08:00 0 [Note] InnoDB: Rollback of trx with id 41833868377 completed
2021-02-08T09:56:48.283572+08:00 0 [Note] InnoDB: Rolling back trx with id 41833864732, 3 rows to undo
2021-02-08T09:56:48.295650+08:00 0 [Note] InnoDB: Rollback of trx with id 41833864732 completed
2021-02-08T09:56:48.295669+08:00 0 [Note] InnoDB: Rolling back trx with id 41833864084, 5 rows to undo
2021-02-08T09:56:48.313279+08:00 0 [Note] InnoDB: Rollback of trx with id 41833864084 completed
2021-02-08T09:56:48.313298+08:00 0 [Note] InnoDB: Rolling back trx with id 41833860883, 34 rows to undo
2021-02-08T09:56:48.395673+08:00 0 [Note] InnoDB: Rollback of trx with id 41833860883 completed
2021-02-08T09:56:48.395691+08:00 0 [Note] InnoDB: Rolling back trx with id 41833859416, 42 rows to undo
2021-02-08T09:56:48.418266+08:00 0 [Note] InnoDB: Rollback of trx with id 41833859416 completed
2021-02-08T09:56:48.418286+08:00 0 [Note] InnoDB: Rolling back trx with id 41833859035, 39 rows to undo
2021-02-08T09:56:48.450000+08:00 0 [Note] InnoDB: Rollback of trx with id 41833859035 completed
2021-02-08T09:56:48.450019+08:00 0 [Note] InnoDB: Rolling back trx with id 41833856831, 6 rows to undo
2021-02-08T09:56:48.459367+08:00 0 [Note] InnoDB: Rollback of trx with id 41833856831 completed
2021-02-08T09:56:48.459390+08:00 0 [Note] InnoDB: Rolling back trx with id 41833856535, 12 rows to undo
2021-02-08T09:56:48.481747+08:00 0 [Note] InnoDB: Rollback of trx with id 41833856535 completed
2021-02-08T09:56:48.481768+08:00 0 [Note] InnoDB: Rolling back trx with id 41833855339, 17 rows to undo
2021-02-08T09:56:48.503463+08:00 0 [Note] Starting crash recovery...
2021-02-08T09:56:48.503526+08:00 0 [Note] InnoDB: Starting recovery for XA transactions...
2021-02-08T09:56:48.503544+08:00 0 [Note] InnoDB: Transaction 41833873061 in prepared state after recovery
2021-02-08T09:56:48.503551+08:00 0 [Note] InnoDB: Transaction contains changes to 1 rows
2021-02-08T09:56:48.503560+08:00 0 [Note] InnoDB: 1 transactions in prepared state after recovery
2021-02-08T09:56:48.503564+08:00 0 [Note] Found 1 prepared transaction(s) in InnoDB
2021-02-08T09:56:48.504007+08:00 0 [Note] Crash recovery finished.
2021-02-08T09:56:48.527891+08:00 0 [Note] InnoDB: Rollback of trx with id 41833855339 completed
2021-02-08T09:56:48.527912+08:00 0 [Note] InnoDB: Rolling back trx with id 41833853129, 33 rows to undo
2021-02-08T09:56:48.586644+08:00 0 [Note] InnoDB: Rollback of trx with id 41833853129 completed
2021-02-08T09:56:48.586666+08:00 0 [Note] InnoDB: Rolling back trx with id 41833848250, 50 rows to undo
2021-02-08T09:56:48.628308+08:00 0 [Note] InnoDB: Rollback of trx with id 41833848250 completed
2021-02-08T09:56:48.628329+08:00 0 [Note] InnoDB: Rolling back trx with id 41833847069, 32 rows to undo
2021-02-08T09:56:48.736507+08:00 0 [Note] InnoDB: Rollback of trx with id 41833847069 completed
2021-02-08T09:56:48.736526+08:00 0 [Note] InnoDB: Rolling back trx with id 41833846771, 19 rows to undo
2021-02-08T09:56:48.762219+08:00 0 [Note] InnoDB: Rollback of trx with id 41833846771 completed
2021-02-08T09:56:48.762240+08:00 0 [Note] InnoDB: Rolling back trx with id 41833844789, 21 rows to undo
2021-02-08T09:56:48.792876+08:00 0 [Note] InnoDB: Rollback of trx with id 41833844789 completed
2021-02-08T09:56:48.792896+08:00 0 [Note] InnoDB: Rolling back trx with id 41833844554, 45 rows to undo
2021-02-08T09:56:48.800731+08:00 0 [Note] InnoDB: Rollback of trx with id 41833844554 completed
2021-02-08T09:56:48.800750+08:00 0 [Note] InnoDB: Rolling back trx with id 41833843201, 66 rows to undo
2021-02-08T09:56:48.857387+08:00 0 [Note] InnoDB: Rollback of trx with id 41833843201 completed
2021-02-08T09:56:48.857410+08:00 0 [Note] InnoDB: Rolling back trx with id 41833835814, 42 rows to undo
2021-02-08T09:56:48.892386+08:00 0 [Note] InnoDB: Rollback of trx with id 41833835814 completed
2021-02-08T09:56:48.892411+08:00 0 [Note] InnoDB: Rolling back trx with id 41833834216, 98 rows to undo
2021-02-08T09:56:48.995226+08:00 0 [Note] InnoDB: Rollback of trx with id 41833834216 completed
2021-02-08T09:56:48.995248+08:00 0 [Note] InnoDB: Rolling back trx with id 41833833954, 120 rows to undo
2021-02-08T09:56:49.023795+08:00 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
2021-02-08T09:56:49.024024+08:00 0 [Note] Server hostname (bind-address): '*'; port: 9306
2021-02-08T09:56:49.024069+08:00 0 [Note] IPv6 is available.
2021-02-08T09:56:49.024083+08:00 0 [Note] - '::' resolves to '::';
2021-02-08T09:56:49.024102+08:00 0 [Note] Server socket created on IP: '::'.
2021-02-08T09:56:49.038050+08:00 0 [Warning] Recovery from master pos 195649390 and file mysql-bin.003048 for channel ''. Previous relay log pos and relay log file had been set to 4, /data/mysqldata/93306/data/relay-bin.001127 respectively.
2021-02-08T09:56:49.038600+08:00 2 [Warning] Storing MySQL user name or password information in the master info repository is not secure and is therefore not recommended. Please consider using the USER and PASSWORD connection options for START SLAVE; see the 'START SLAVE Syntax' in the MySQL Manual for more information.
2021-02-08T09:56:49.038815+08:00 2 [ERROR] Slave I/O for channel '': error connecting to master 'synuser9@10.253.47.197:9306' - retry-time: 60 retries: 1, Error_code: 2003
2021-02-08T09:56:49.051214+08:00 1 [Note] Slave SQL thread for channel '' initialized, starting replication in log 'mysql-bin.003048' at position 195649390, relay log '/data/mysqldata/93306/data/relay-bin.001128' position: 4
2021-02-08T09:56:49.065090+08:00 0 [Note] Event Scheduler: Loaded 0 events
2021-02-08T09:56:49.065239+08:00 0 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.7.32-log' socket: '/data/mysqldata/93306/tmp/mysql.sock' port: 9306 MySQL Community Server (GPL)
2021-02-08T09:56:49.237415+08:00 0 [Note] InnoDB: Rollback of trx with id 41833833954 completed
2021-02-08T09:56:49.237437+08:00 0 [Note] InnoDB: Rolling back trx with id 41833832102, 34 rows to undo
2021-02-08T09:56:49.266657+08:00 0 [Note] InnoDB: Rollback of trx with id 41833832102 completed
2021-02-08T09:56:49.266678+08:00 0 [Note] InnoDB: Rolling back trx with id 41833829225, 66 rows to undo
2021-02-08T09:56:49.339730+08:00 0 [Note] InnoDB: Rollback of trx with id 41833829225 completed
2021-02-08T09:56:49.339750+08:00 0 [Note] InnoDB: Rolling back trx with id 41833821868, 65 rows to undo
2021-02-08T09:56:49.433837+08:00 0 [Note] InnoDB: Rollback of trx with id 41833821868 completed
2021-02-08T09:56:49.433865+08:00 0 [Note] InnoDB: Rolling back trx with id 41833815095, 32 rows to undo
2021-02-08T09:56:49.482764+08:00 0 [Note] InnoDB: Rollback of trx with id 41833815095 completed
2021-02-08T09:56:49.482783+08:00 0 [Note] InnoDB: Rolling back trx with id 41833771855, 1 rows to undo
2021-02-08T09:56:49.483077+08:00 0 [Note] InnoDB: Rollback of trx with id 41833771855 completed
2021-02-08T09:56:49.483097+08:00 0 [Note] InnoDB: Rolling back trx with id 41833766384, 13 rows to undo
2021-02-08T09:56:49.483428+08:00 0 [Note] InnoDB: Rollback of trx with id 41833766384 completed
2021-02-08T09:56:49.483451+08:00 0 [Note] InnoDB: Rolling back trx with id 41833765159, 4 rows to undo
2021-02-08T09:56:49.483793+08:00 0 [Note] InnoDB: Rollback of trx with id 41833765159 completed
2021-02-08T09:56:49.483818+08:00 0 [Note] InnoDB: Rolling back trx with id 41833764645, 8 rows to undo
2021-02-08T09:56:49.484133+08:00 0 [Note] InnoDB: Rollback of trx with id 41833764645 completed
2021-02-08T09:56:49.484156+08:00 0 [Note] InnoDB: Rolling back trx with id 41833764629, 4 rows to undo
2021-02-08T09:56:49.484406+08:00 0 [Note] InnoDB: Rollback of trx with id 41833764629 completed
2021-02-08T09:56:49.484426+08:00 0 [Note] InnoDB: Rolling back trx with id 41833764617, 54 rows to undo
2021-02-08T09:56:49.532864+08:00 0 [Note] InnoDB: Rollback of trx with id 41833764617 completed
2021-02-08T09:56:49.532880+08:00 0 [Note] InnoDB: Rolling back trx with id 41833764470, 11 rows to undo
2021-02-08T09:56:49.533191+08:00 0 [Note] InnoDB: Rollback of trx with id 41833764470 completed
2021-02-08T09:56:49.533208+08:00 0 [Note] InnoDB: Rolling back trx with id 41833764374, 6 rows to undo
2021-02-08T09:56:49.533459+08:00 0 [Note] InnoDB: Rollback of trx with id 41833764374 completed
2021-02-08T09:56:49.533479+08:00 0 [Note] InnoDB: Rolling back trx with id 41833764362, 32 rows to undo
2021-02-08T09:56:49.556440+08:00 0 [Note] InnoDB: Rollback of trx with id 41833764362 completed
2021-02-08T09:56:49.556459+08:00 0 [Note] InnoDB: Rolling back trx with id 41833754939, 61 rows to undo
2021-02-08T09:56:49.599040+08:00 0 [Note] InnoDB: Rollback of trx with id 41833754939 completed
2021-02-08T09:56:49.599059+08:00 0 [Note] InnoDB: Rollback of non-prepared transactions completed
处理思路
因为报错日志上面有一个表名INSERT INTO I_USER_ORDER_280，所以让业务把有关于这个表的连接停止掉，数据库果然不重启。
我另外在这个库加了一个全局读锁，FLUSH TABLES WITH READ LOCK后 数据库也不重启，所以初步怀疑是 I_USER_ORDER_280这个表损坏了。
处理方法：
业务停止全部连接，把这个表使用mysqldump导出后，重新导入(.sql文件会先删除再创建表)。后来数据库也不重启了。
网友评论