FLUSH LOGS safely rotates the binlog.
Davide Giunchi wrote:
You are right, but my master generate about 150Mb of binlog x day, i a slave
fail after 4 day it will reexec a lot of query and take some time. how can i
safely rotate the log in master+slaves without restarting them?
The Mysql
-
From: Davide Giunchi [SMTP:[EMAIL PROTECTED]]
Sent: Wednesday, April 10, 2002 5:37 PM
To: Marc Prewitt
Cc: [EMAIL PROTECTED]
Subject:Re: binlog and replication stuff
You are right, but my master generate about 150Mb
FLUSH LOGS in the master and all is ok? binlog will be rotate and slaves will
see it, continue to work and update master.info?
Regads
Il 15:31, giovedì 11 aprile 2002, hai scritto:
FLUSH LOGS safely rotates the binlog.
Davide Giunchi wrote:
You are right, but my master generate about
Yes.
Davide Giunchi wrote:
FLUSH LOGS in the master and all is ok? binlog will be rotate and slaves will
see it, continue to work and update master.info?
Regads
Il 15:31, giovedì 11 aprile 2002, hai scritto:
FLUSH LOGS safely rotates the binlog.
Davide Giunchi wrote:
You are
]]
Sent: Wednesday, April 10, 2002 5:37 PM
To: Marc Prewitt
Cc: [EMAIL PROTECTED]
Subject:Re: binlog and replication stuff
You are right, but my master generate about 150Mb of binlog x day, i
a slave
fail after 4 day it will reexec a lot
When a slave crashes or reboots, it should start replicating from where it
left off--at least ours do work that way. The current replication state
is saved in master.info on the slave and when it starts up again, it
should read that file and resume reading the binlog on the master where it
left
Hello.
I'm using MySQL-3.23.38 on 5 RedHat 7.1/7.2 servers composed by one master
and 4 mysql slave, every write is made on the master and then replicated to
the slave.
The problem is that if one client crash or must be rebooted i've to:
- on the mysql master stop mysql, delete binlogfile, tar
