Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5.16
-
None
-
None
-
centos 7.8
Description
My production server was suddenly hanging after shutdown. I just executed some normal SQL statements, and turned on semi-synchronous replication.
2022-11-19 16:26:47 0 [Note] /home/sql/bin/mysqld: ready for connections.
|
Version: '10.5.16-MariaDB-log' socket: '/data/mysql.sock' port: 3306 MairaDB Community Server - (GPL)
|
2022-11-19 16:26:50 5 [Note] Semi-sync replication switched OFF.
|
2022-11-19 16:26:50 5 [Note] Semi-sync replication disabled on the master.
|
2022-11-19 16:26:50 5 [Note] Enable Semi-sync Master after reset master
|
2022-11-19 16:26:50 5 [Note] Semi-sync replication initialized for transactions.
|
2022-11-19 16:26:50 5 [Note] Semi-sync replication enabled on the master.
|
2022-11-19 16:27:00 6 [Warning] Timeout waiting for reply of binlog (file: mysql-bin.000001, pos: 512), semi-sync up to file , position 0.
|
2022-11-19 16:27:00 6 [Note] Semi-sync replication switched OFF.
|
2022-11-19 16:27:00 6 [Warning] 'user' entry '@cr1' ignored in --skip-name-resolve mode.
|
2022-11-19 16:27:00 6 [Warning] 'proxies_priv' entry '@% root@cr1' ignored in --skip-name-resolve mode.
|
2022-11-19 16:27:07 7 [Note] Start binlog_dump to slave_server(4640), pos(, 4), using_gtid(1), gtid('')
|
2022-11-19 16:27:07 7 [Note] Start semi-sync binlog_dump to slave (server_id: 4640), pos(./mysql-bin.000001, 4)
|
2022-11-19 16:27:07 1 [Note] Semi-sync replication switched ON with slave (server_id: 4640) at (mysql-bin.000001, 1807)
|
2022-11-19 16:27:22 8 [Note] Start binlog_dump to slave_server(8101), pos(, 4), using_gtid(1), gtid('')
|
2022-11-19 16:28:09 0 [Note] /home/sql/bin/mysqld (initiated by: root[root] @ [192.168.1.101]): Normal shutdown
|
2022-11-19 16:28:09 0 [Note] Event Scheduler: Purging the queue. 0 events
|
2022-11-19 16:28:11 1 [Note] Stopping ack receiver thread
|