mysql5.7.38版本，丛库，自动重启(不频繁)，重启时间点日志如下
2025-05-18T09:34:51.283927+08:00 2 [Note] Multi-threaded slave statistics for channel ‘’: seconds elapsed = 120; events assigned = 351284225; worker queues filled over ove
rrun level = 9394; waited due a Worker queue full = 815; waited due the total size = 0; waited at clock conflicts = 2360659386600 waited (count) when Workers occupied = 22
55553 waited when Workers occupied = 32392269900
2025-05-18T09:35:58.239722+08:00 0 [Warning] option ‘max_binlog_size’: unsigned value 2147483648 adjusted to 1073741824
2025-05-18T09:35:58.239847+08:00 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled
2025-05-18T09:35:58.239877+08:00 0 [Note] /app/mysqlsoft/bin/mysqld (mysqld 5.7.38-log) starting as process 74802 …
2025-05-18T09:35:58.277887+08:00 0 [Note] InnoDB: PUNCH HOLE support available
2025-05-18T09:35:58.277915+08:00 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2025-05-18T09:35:58.277920+08:00 0 [Note] InnoDB: Uses event mutexes
2025-05-18T09:35:58.277925+08:00 0 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
2025-05-18T09:35:58.277928+08:00 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2025-05-18T09:35:58.277932+08:00 0 [Note] InnoDB: Using Linux native AIO
2025-05-18T09:35:58.278333+08:00 0 [Note] InnoDB: Number of pools: 1
2025-05-18T09:35:58.278405+08:00 0 [Note] InnoDB: Using CPU crc32 instructions
2025-05-18T09:35:58.279673+08:00 0 [Note] InnoDB: Initializing buffer pool, total size = 312G, instances = 52, chunk size = 128M
2025-05-18T09:36:10.542820+08:00 0 [Note] InnoDB: Completed initialization of buffer pool
2025-05-18T09:36:11.893156+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(
).
2025-05-18T09:36:11.906306+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2025-05-18T09:36:12.833968+08:00 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 16713962393580
2025-05-18T09:36:12.868426+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16713967635968
2025-05-18T09:36:12.935205+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16713972878848
2025-05-18T09:36:12.972060+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16713978121728
2025-05-18T09:36:13.009988+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16713983364608
2025-05-18T09:36:13.047141+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16713988607488
2025-05-18T09:36:13.086129+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16713993850368
2025-05-18T09:36:13.124271+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16713999093248
2025-05-18T09:36:13.165807+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714004336128
2025-05-18T09:36:13.212065+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714009579008
2025-05-18T09:36:13.249746+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714014821888
2025-05-18T09:36:13.290415+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714020064768
2025-05-18T09:36:13.334169+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714025307648
2025-05-18T09:36:13.375485+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714030550528
2025-05-18T09:36:13.414285+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714035793408
2025-05-18T09:36:13.453775+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714041036288
2025-05-18T09:36:13.496697+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714046279168
2025-05-18T09:36:13.536017+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714051522048
2025-05-18T09:36:13.574104+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714056764928
2025-05-18T09:36:13.614325+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714062007808
2025-05-18T09:36:13.654551+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714067250688
2025-05-18T09:36:13.697822+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714072493568
2025-05-18T09:36:13.732151+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714077736448
2025-05-18T09:36:13.774065+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714082979328
2025-05-18T09:36:13.811078+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714088222208
2025-05-18T09:36:13.850215+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714093465088
2025-05-18T09:36:13.890718+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714098707968
2025-05-18T09:36:13.930204+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714103950848
2025-05-18T09:36:13.968773+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714109193728
2025-05-18T09:36:14.008667+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714114436608
2025-05-18T09:36:14.047950+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714119679488
2025-05-18T09:36:14.083705+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714124922368
2025-05-18T09:36:14.122459+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714130165248
2025-05-18T09:36:14.160139+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714135408128
2025-05-18T09:36:14.197967+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714140651008
2025-05-18T09:36:14.243758+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714145893888
2025-05-18T09:36:14.284512+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714151136768
2025-05-18T09:36:14.327694+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714156379648
2025-05-18T09:36:14.363808+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714161622528
2025-05-18T09:36:14.404871+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714166865408
2025-05-18T09:36:14.446247+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714172108288
2025-05-18T09:36:14.484852+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714177351168
2025-05-18T09:36:14.524344+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714182594048
2025-05-18T09:36:14.562631+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714187836928
2025-05-18T09:36:14.601943+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714193079808
2025-05-18T09:36:14.648659+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714198322688
2025-05-18T09:36:14.686221+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714203565568
2025-05-18T09:36:14.726842+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714208808448
2025-05-18T09:36:14.768002+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714214051328
2025-05-18T09:36:14.808471+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714219294208
2025-05-18T09:36:14.851095+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714224537088
2025-05-18T09:36:14.894941+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714229779968
2025-05-18T09:36:14.936601+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714235022848
2025-05-18T09:36:14.974211+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714240265728
2025-05-18T09:36:15.011763+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714245508608
2025-05-18T09:36:15.048111+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714250751488
2025-05-18T09:36:15.086331+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714255994368
2025-05-18T09:36:15.125286+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714261237248
2025-05-18T09:36:15.165469+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714266480128
2025-05-18T09:36:15.205539+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714271723008
2025-05-18T09:36:15.244799+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714276965888
2025-05-18T09:36:15.282635+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714282208768
2025-05-18T09:36:15.324041+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714287451648
2025-05-18T09:36:15.359978+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714292694528
2025-05-18T09:36:15.402172+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714297937408
2025-05-18T09:36:15.443631+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714303180288
2025-05-18T09:36:15.484156+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714308423168
2025-05-18T09:36:15.528006+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714313666048
2025-05-18T09:36:15.568822+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714318908928
2025-05-18T09:36:15.610612+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714324151808
2025-05-18T09:36:15.647254+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714329394688
2025-05-18T09:36:15.684624+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714334637568
2025-05-18T09:36:15.729710+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714339880448
2025-05-18T09:36:15.756790+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714345123328
2025-05-18T09:36:15.780653+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714350366208
2025-05-18T09:36:15.805182+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714355609088
2025-05-18T09:36:15.830280+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714360851968
2025-05-18T09:36:15.859536+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714366094848
2025-05-18T09:36:15.901398+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714371337728
2025-05-18T09:36:15.944449+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714376580608
2025-05-18T09:36:15.993916+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714381823488
2025-05-18T09:36:16.031992+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714387066368
2025-05-18T09:36:16.067595+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714392309248
2025-05-18T09:36:16.103921+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714397552128
2025-05-18T09:36:16.141318+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714402795008
2025-05-18T09:36:16.180050+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714408037888
2025-05-18T09:36:16.217726+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714413280768
2025-05-18T09:36:16.255884+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714418523648
2025-05-18T09:36:16.294019+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714423766528
2025-05-18T09:36:16.329827+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714429009408
2025-05-18T09:36:16.367661+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714434252288
2025-05-18T09:36:16.408664+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714439495168
2025-05-18T09:36:16.443811+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714444738048
2025-05-18T09:36:16.482616+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714449980928
2025-05-18T09:36:16.519859+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714455223808
2025-05-18T09:36:16.558752+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714460466688
2025-05-18T09:36:16.594935+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714465709568
2025-05-18T09:36:16.631614+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714470952448
2025-05-18T09:36:16.669308+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714476195328
2025-05-18T09:36:16.709704+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714481438208
2025-05-18T09:36:16.755648+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714486681088
2025-05-18T09:36:16.788425+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714491923968
2025-05-18T09:36:16.821415+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714497166848
2025-05-18T09:36:16.861373+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714502409728
2025-05-18T09:36:16.901511+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714507652608
2025-05-18T09:36:16.942073+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714512895488
2025-05-18T09:36:16.981761+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714518138368
2025-05-18T09:36:17.019781+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714523381248
2025-05-18T09:36:17.057942+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714528624128
2025-05-18T09:36:17.098988+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714533867008
2025-05-18T09:36:17.140616+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714539109888
2025-05-18T09:36:17.177750+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714544352768
2025-05-18T09:36:17.215161+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714549595648
2025-05-18T09:36:17.255818+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714554838528
2025-05-18T09:36:17.295405+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714560081408
2025-05-18T09:36:17.330821+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714565324288
2025-05-18T09:36:17.368762+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714570567168
2025-05-18T09:36:17.407675+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714575810048
2025-05-18T09:36:17.444987+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714581052928
2025-05-18T09:36:17.483430+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714586295808
2025-05-18T09:36:17.523753+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714591538688
2025-05-18T09:36:17.562330+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714596781568
2025-05-18T09:36:17.601842+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714602024448
2025-05-18T09:36:17.640010+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714607267328
2025-05-18T09:36:17.675996+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714612510208
2025-05-18T09:36:17.715526+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714617753088
2025-05-18T09:36:17.758780+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714622995968
2025-05-18T09:36:17.802243+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714628238848
2025-05-18T09:36:17.837949+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714633481728
2025-05-18T09:36:17.877520+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714638724608
2025-05-18T09:36:17.919959+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714643967488
2025-05-18T09:36:17.956174+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714649210368
2025-05-18T09:36:17.996169+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714654453248
2025-05-18T09:36:18.036210+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714659696128
2025-05-18T09:36:18.075304+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714664939008
2025-05-18T09:36:18.112808+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714670181888
2025-05-18T09:36:18.150888+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714675424768
2025-05-18T09:36:18.194336+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714680667648
2025-05-18T09:36:18.228641+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714685910528
2025-05-18T09:36:18.271802+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714691153408
2025-05-18T09:36:18.318602+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714696396288
2025-05-18T09:36:18.356636+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714701639168
2025-05-18T09:36:18.381442+08:00 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 16714705043129
2025-05-18T09:36:18.381863+08:00 0 [Note] InnoDB: Database was not shutdown normally!
2025-05-18T09:36:18.381868+08:00 0 [Note] InnoDB: Starting crash recovery.
2025-05-18T09:36:18.922887+08:00 0 [Note] InnoDB: Transaction 16422942381 was in the XA prepared state.
2025-05-18T09:36:18.924281+08:00 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo
2025-05-18T09:36:18.924293+08:00 0 [Note] InnoDB: Trx id counter is 16422942720
2025-05-18T09:36:18.924388+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
2025-05-18T09:36:31.720905+08:00 0 [Note] InnoDB: Apply batch completed
2025-05-18T09:36:31.720955+08:00 0 [Note] InnoDB: Last MySQL binlog file position 0 746546119, file name mysql-bin.021811
2025-05-18T09:36:32.133770+08:00 0 [Note] InnoDB: Starting in background the rollback of uncommitted transactions
2025-05-18T09:36:32.133802+08:00 0 [Note] InnoDB: Rollback of non-prepared transactions completed
2025-05-18T09:36:32.377922+08:00 0 [Note] InnoDB: Removed temporary tablespace data file: “ibtmp1”
2025-05-18T09:36:32.377953+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2025-05-18T09:36:32.378000+08:00 0 [Note] InnoDB: Setting file ‘./ibtmp1’ size to 12 MB. Physically writing the file full; Please wait …
2025-05-18T09:36:32.384602+08:00 0 [Note] InnoDB: File ‘./ibtmp1’ size is now 12 MB.
2025-05-18T09:36:32.385187+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2025-05-18T09:36:32.385198+08:00 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2025-05-18T09:36:32.385458+08:00 0 [Note] InnoDB: Waiting for purge to start
2025-05-18T09:36:32.435618+08:00 0 [Note] InnoDB: 5.7.38 started; log sequence number 16714705043129
2025-05-18T09:36:32.435635+08:00 0 [Note] InnoDB: page_cleaner: 1000ms intended loop took 20543ms. The settings might not be optimal. (flushed=0 and evicted=0, during the
time.)
2025-05-18T09:36:32.436184+08:00 0 [Note] InnoDB: Loading buffer pool(s) from /data/mysqldata/ib_buffer_pool
2025-05-18T09:36:32.436777+08:00 0 [Note] Plugin ‘FEDERATED’ is disabled.
2025-05-18T09:36:32.462759+08:00 0 [ERROR] Function ‘validate_password’ already exists
2025-05-18T09:36:32.462770+08:00 0 [Warning] Couldn’t load plugin named ‘validate_password’ with soname ‘validate_password.so’.
2025-05-18T09:36:32.462923+08:00 0 [Note] Semi-sync replication initialized for transactions.
2025-05-18T09:36:32.462931+08:00 0 [Note] Semi-sync replication enabled on the master.
2025-05-18T09:36:32.462972+08:00 0 [Note] Starting ack receiver thread
2025-05-18T09:36:32.470708+08:00 0 [Note] Recovering after a crash using /data/mysqlbinlog/mysql-bin
2025-05-18T09:36:33.665836+08:00 0 [Note] InnoDB: Buffer pool(s) load completed at 250518 9:36:33
2025-05-18T09:36:34.292111+08:00 0 [Note] Starting crash recovery…
2025-05-18T09:36:34.292162+08:00 0 [Note] InnoDB: Starting recovery for XA transactions…
2025-05-18T09:36:34.292170+08:00 0 [Note] InnoDB: Transaction 16422942381 in prepared state after recovery
2025-05-18T09:36:34.292174+08:00 0 [Note] InnoDB: Transaction contains changes to 2 rows
2025-05-18T09:36:34.292178+08:00 0 [Note] InnoDB: 1 transactions in prepared state after recovery
2025-05-18T09:36:34.292181+08:00 0 [Note] Found 1 prepared transaction(s) in InnoDB
2025-05-18T09:36:34.292390+08:00 0 [Note] Crash recovery finished.
2025-05-18T09:36:35.036112+08:00 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2025-05-18T09:36:35.036133+08:00 0 [Note] Skipping generation of SSL certificates as certificate files are present in data directory.
2025-05-18T09:36:35.036139+08:00 0 [Warning] A deprecated TLS version TLSv1 is enabled. Please use TLSv1.2 or higher.
2025-05-18T09:36:35.036142+08:00 0 [Warning] A deprecated TLS version TLSv1.1 is enabled. Please use TLSv1.2 or higher.
2025-05-18T09:36:35.037080+08:00 0 [Warning] CA certificate ca.pem is self signed.
2025-05-18T09:36:35.037120+08:00 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
2025-05-18T09:36:35.037301+08:00 0 [Note] Server hostname (bind-address): ‘0.0.0.0’; port: 13306
2025-05-18T09:36:35.037325+08:00 0 [Note] - ‘0.0.0.0’ resolves to ‘0.0.0.0’;
2025-05-18T09:36:35.037344+08:00 0 [Note] Server socket created on IP: ‘0.0.0.0’.
2025-05-18T09:36:35.050690+08:00 0 [Warning] Recovery from master pos 968531274 and file mysql-bin.021946 for channel ‘’. Previous relay log pos and relay log file had bee
n set to 968531487, /data/mysqlbinlog/mysql-relay-bin.065808 respectively.
2025-05-18T09:36:35.051050+08:00 1 [Note] Slave I/O thread: Start semi-sync replication to master ‘repl@172.20.20.3:13306’ in log ‘mysql-bin.021946’ at position 968531274
2025-05-18T09:36:35.051083+08:00 1 [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.
2025-05-18T09:36:35.051397+08:00 1 [Note] Slave I/O thread for channel ‘’: connected to master ‘repl@172.20.20.3:13306’,replication started in log ‘mysql-bin.021946’ at po
sition 968531274
2025-05-18T09:36:35.054481+08:00 2 [Note] Slave SQL thread for channel ‘’ initialized, starting replication in log ‘mysql-bin.021946’ at position 968531274, relay log ‘/da
ta/mysqlbinlog/mysql-relay-bin.065809’ position: 4
2025-05-18T09:36:35.065457+08:00 0 [Note] Event Scheduler: Loaded 0 events
2025-05-18T09:36:35.065559+08:00 0 [Note] /app/mysqlsoft/bin/mysqld: ready for connections.
Version: ‘5.7.38-log’ socket: ‘/app/mysqlsoft/mysql.sock’ port: 13306 MySQL Community Server (GPL)
2025-05-18T09:36:46.651734+08:00 3 [Warning] Timeout waiting for reply of binlog (file: mysql-bin.021812, pos: 895), semi-sync up to file , position 0.
2025-05-18T09:36:46.651758+08:00 3 [Note] Semi-sync replication switched OFF.
2025-05-18T09:38:35.358003+08:00 2 [Note] Multi-threaded slave statistics for channel ‘’: seconds elapsed = 120; events assigned = 553985; worker queues filled over overru
n level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts = 26915217000 waited (count) when Workers occupied = 2305 waited
when Workers occupied = 484234900
2025-05-18T09:40:35.298057+08:00 2 [Note] Multi-threaded slave statistics for channel ‘’: seconds elapsed = 120; events assigned = 922625; worker queues filled over overru
n level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts = 29838338200 waited (count) when Workers occupied = 2327 waited
when Workers occupied = 488233900
2025-05-18T09:42:35.257588+08:00 2 [Note] Multi-threaded slave statistics for channel ‘’: seconds elapsed = 120; events assigned = 1289217; worker queues filled over overr
un level = 0; waited due a Worker queue full = 0; waited due the total size = 0; waited at clock conflicts = 32608315100 waited (count) when Workers occupied = 2444 waited
when Workers occupied = 508056000
主库的binlog mysql-bin.021812是不是被清理了
主库没有被清理这个日志
看日志，这个时间点已经重启了。建议看一下这个时间段的系统相关日志
主库日志被清 了
数据库重启前的mysqld.log日志呢