Here's another way to do it which works well with multiple slaves:
http://mtop.sourceforge.net/utils/purge_replication_log
This script is run on the slave and the master. When run on the slave it
updates a table in the master which keeps track of the log position for
each slave. When run on
hi all
i have established a two way replication setup
my problem is that my hard disk gets occupied by the log files;
i tried purging the files but after some time again my hard disk gets filled
with the log files
could any one please tell me how to manage the log files.
thanks
anirudh
mysql,
I too would be interested in a good way of clearing the binary log files
(preferably non disruptive to the server ;-)
The only thing thats saving me so far is that the systems capacity is 320Gb.
danny
Anirudha Kukreti wrote:
hi all
i have established a two way replication setup
my problem is
Danny Haworth wrote:
I too would be interested in a good way of clearing the binary log files
(preferably non disruptive to the server ;-)
The only thing thats saving me so far is that the systems capacity is 320Gb.
danny
Anirudha Kukreti wrote:
hi all
i have established a two way
I have a fairly complicated one-way replication set-up, whereby we have
multiple master servers and multiple slaves, all replicating unrelated
databases from one to another.
It's set up and works, but not reliably. Pretty much every day I come into
work to find one machine is no longer
