Re: SLAVE aware of binary log file switch?
Am 17.06.2013 13:11, schrieb Mihamina Rakotomandimby: Say the binary log file (on the master) has reached its maximum size, so that it has to switch to a +1 binary log file: does he inform the SLAVE of that switch so that the SLAVE updates its information about the MASTER status? The master does not inform the slave via an immediate communication channel, but the slave knows how to keep up because the end of the binary log file contains continuation information - i.e. the name of the next log file to fetch. Denis -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: SLAVE aware of binary log file switch?
On 2013-06-17 14:43, Denis Jedig wrote: Say the binary log file (on the master) has reached its maximum size, so that it has to switch to a +1 binary log file: does he inform the SLAVE of that switch so that the SLAVE updates its information about the MASTER status? The master does not inform the slave via an immediate communication channel, but the slave knows how to keep up because the end of the binary log file contains continuation information - i.e. the name of the next log file to fetch. OK. I'm sorry I was mislead by the output of: [mihamina@prod-ebidual ~]$ echo SHOW SLAVE STATUS \G; | mysql -uroot -px | grep 'Slave_' Slave_IO_State: Waiting for master to send event -- this Slave_IO_Running: Yes Slave_SQL_Running: Yes -- RMA.
RE: SLAVE aware of binary log file switch?
Waiting for master to send event -- just means that nothing is being replicated at the moment. The Yes+Yes says that things are running. Seconds_behind_master = 0 says that the Slave is essentially caught up. NULL means something is broken. 0 _may_ indicate a problem, or it may indicate a brief delay. -Original Message- From: Mihamina Rakotomandimby [mailto:miham...@rktmb.org] Sent: Monday, June 17, 2013 5:35 AM To: mysql@lists.mysql.com Subject: Re: SLAVE aware of binary log file switch? On 2013-06-17 14:43, Denis Jedig wrote: Say the binary log file (on the master) has reached its maximum size, so that it has to switch to a +1 binary log file: does he inform the SLAVE of that switch so that the SLAVE updates its information about the MASTER status? The master does not inform the slave via an immediate communication channel, but the slave knows how to keep up because the end of the binary log file contains continuation information - i.e. the name of the next log file to fetch. OK. I'm sorry I was mislead by the output of: [mihamina@prod-ebidual ~]$ echo SHOW SLAVE STATUS \G; | mysql -uroot - px | grep 'Slave_' Slave_IO_State: Waiting for master to send event -- this Slave_IO_Running: Yes Slave_SQL_Running: Yes -- RMA.