Well,
I supposed that your slave is broken from now, because your bin-log
is not the exact situation of your databases. So:
1) no. If your slave is stopped for a abrupt lost of connection to your
master, the old binlogs cannot do anything about. You need to copy the
databases from your master to your slave before start it, and, with this,
have a real database replication.
2) no. When you started, mysqld will create a new for you.
3) yes. Stop the slaves to copy the databases and rebuild your replication.
-Original Message-
From: Jeff [mailto:[EMAIL PROTECTED]
Sent: Monday, March 06, 2006 12:00 PM
To: mysql@lists.mysql.com
Subject: Changing the binlog dir
Hello all,
I had a problem last night where my Master server filled up the /var/
partition and stopped logging to the bin log. This caused all sorts of
havok on my slaves and replication. My bad for not watching this but now
what I'd like to do is move where MySQL writes the binlog to. Currently
it's in the default /var/lib/mysql but I'd like to move it where I
actually have the database files which is on a much larger partition.
From what I've read I can put --log-bin=/data/hostname-bin into the
my.cnf and restart the mysql server.
Questions:
1) do I have to move the old binlogs to the /data/ prior to restarting
mysql
2) should I move the binlog index as well?
3) will moving the binlog location throw the slaves off?
Thanks,
Jeff
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
