On Friday 24 August 2001 00:09, Jeremy Zawodny wrote:
> On Thu, Aug 23, 2001 at 01:15:25PM -0400, Robinson, Mike wrote:
> >
> > I just set up a master/slave replication scheme and all is well, but
> > through the procedure did get bit on the tail.
> > 
> > After the setup, and after the master and slave mysql servers had
> > been started, I got some error messages that pointed to a type in
> > the slave's my.cnf file. I shut the slave down, fixed the typo, and
> > restarted. Got the same error.
> > 
> > I had a look at the master.info, and noticed it contained old
> > information from the previous my.cnf. There were no binary log
> > entries in it, so I shut the slave down, deleted the master.info,
> > and restarted the slave. This fixed the problem and they're
> > replicating fine. (A terrific feature, my thanks to the mysql team
> > for that one.)
> > 
> > Question is, is this behaviour by design? Seems to me if you edit
> > my.cnf and restart the mysql slave the master.info entries
> > corresponding to the my.cnf file should be updated.  Thanks for any
> > insight.
> 
> That's a common problem.  Very common.  You have to remove the
> master.info file, or edit it by hand. :-(
> 
> I've called it a bug several times in the past, but it occurs to me
> that I may have never told the person who wrote the replication code.
> So...
> 
> Sasha: Can this be fixed?  In my mind it's a bug.  One that has bitten
>        too many people already.
> 
> If not, we at least to get it documented here:
> 
>   http://www.mysql.com/doc/R/e/Replication_Features.html
> 
> Thoughts?

It is a feature that needs to be better documented. The main reason 
master.info is more authoritative that my.cnf is to support dynamic master 
changes. That is if you did CHANGE MASTER TO a different host, you want to 
continue replicating from that new master if you restart the slave in the 
middle.

The options in my.cnf should really be called default-master-host, 
default-master-port, etc, but it is too late to change now - it would cause 
more problems that it would solve. In fact, we should probably change the 
replication HOWTO to suggest CHANGE MASTER TO command for replication setup 
instead of using my.cnf options. The recommended procedure to change masters 
is also to use CHANGE MASTER TO command.

> 
> Thanks,
> 
> Jeremy
> -- 
> Jeremy D. Zawodny, <[EMAIL PROTECTED]>
> Technical Yahoo - Yahoo Finance
> Desk: (408) 349-7878   Fax: (408) 349-5454   Cell: (408) 685-5936
> 
> MySQL 3.23.41-max: up 6 days, processed 88,944,778 queries (148/sec. avg)
> 

Jeremy, your server has been slowing down - it started out at 154 queries per 
second, and now is down to 148 :-)

-- 
MySQL Development Team
For technical support contracts, visit https://order.mysql.com/
   __  ___     ___ ____  __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
       <___/                  

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to