Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.1.1
-
None
-
maxscale-1.1.1-2.x86_64
Centos 6.6
mysql 5.6.24-log
Description
Hi,
I restarted the master database server and on the slave servers which are connecting to the MaxScale Binlog servers I could see a lot of weird characters in the slave status but the replication is working.
Master_Log_File: mysql-bin.004821A���
Read_Master_Log_Pos: 135635651
Relay_Log_File: mysql-relay-bin.000090
Relay_Log_Pos: 30742929
Relay_Master_Log_File: mysql-bin.004821A���
I checked the master status on master, that one is fine:
show master status;
------------------------------------------------------------------------
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
------------------------------------------------------------------------
| mysql-bin.004821 | 139901230 |
------------------------------------------------------+-----------------
Master status on binlog server is fine:
show master status;
-----------------------------------------------------------------------
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Execute_Gtid_Set |
-----------------------------------------------------------------------
| mysql-bin.004821 | 143078963 |
-----------------------------------------------------------------------
Slave status on binlog server is fine:
Master_Log_File: mysql-bin.004821
Read_Master_Log_Pos: 144237107
Relay_Log_File: mysql-bin.004821
Relay_Log_Pos: 144237107
Relay_Master_Log_File: mysql-bin.004821
The file on the binlog server is fine:
rw-rw---. 1 root root 141948913 Jul 30 09:43 mysql-bin.004821
So everything is fine except the binlog file names on the slaves which are connecting to the binlog server.
If I stop the slave on the slave server and I restart it the file names will be fine again.
It did not cause any problems but it is weird and I could not find any report about this problem.
Thanks