MySQL Forums
Forum List  »  Replication

Important: Status of master binlog dump thread is not proper it seems?
Posted by: shahid hussain
Date: March 21, 2014 12:13AM

Hi,
I have one doubt. MysqlBinlog dump thread transfers the packet to slave I/O thread. In below result binlog dum thread is telling that it has sent all events to slave but in slave output you can see ,slave has not read all events. (see show master and slave status below).

My doubt is, binlog dump thread is telling it has transferred all events(fcab0e0a-9796-11e3-9f59-5254006e4bc5:1-387)and since slave I/O is stopped due to some error so it has retrieved only till fcab0e0a-9796-11e3-9f59-5254006e4bc5:1-384. so where remaining events went? is there a packet loss ?


please let me get out from this confusion, suggest me if i m wrong.

AT MASTER SERVER:
mysql> show master status;
+------------------+----------+--------------+------------------+--------------------------------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+--------------------------------------------+
| mysql-bin.000026 | 923 | sile,testdb | | fcab0e0a-9796-11e3-9f59-5254006e4bc5:1-387 |
+------------------+----------+--------------+------------------+--------------------------------------------+
1 row in set (0.00 sec)

mysql> show processlist\G;
Id: 52
User: rehana
Host: 172.20.0.225:49976
db: NULL
Command: Binlog Dump GTID
Time: 121
State: Master has sent all binlog to slave; waiting for binlog to be updated
Info: NULL

No query specified

AT SLAVE SERVER:
Last_IO_Errno: 1595
Last_IO_Error: Relay log write failure: could not queue event from master
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 1
Master_UUID: fcab0e0a-9796-11e3-9f59-5254006e4bc5
Master_Info_File: mysql.slave_master_info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp: 140321 11:09:49
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set: fcab0e0a-9796-11e3-9f59-5254006e4bc5:379-384
Executed_Gtid_Set: 01372b42-a9cc-11e3-9613-525400d8d607:1-15,
fcab0e0a-9796-11e3-9f59-5254006e4bc5:1-384

Options: ReplyQuote


Subject
Views
Written By
Posted
Important: Status of master binlog dump thread is not proper it seems?
4527
March 21, 2014 12:13AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.