Brown, Charles wrote:
Mysql Replication is not scope to one database. Rather it was intended
for the entire instance. The slave reads its master's transaction log
and applies those changes. Before it applies the changes, it will query
the master just to make sure the values are the same -- meaning the
master and slave are insyn. Interesting hand-shaking.
Thanks

Not so, as far as I know. The binary log is copied to the slave, written to the "relay log" on disk, and then another thread on the slave reads and executes from the relay log. It trusts the relay log and doesn't further communicate with the master.

If you want to know if a slave is identical to its master, I know of no other way to do it than checksumming the data. I wrote MySQL Table Checksum for this purpose (http://sourceforge.net/projects/mysqltoolkit).

Regards
Baron





-----Original Message-----
From: Baron Schwartz [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 24, 2007 9:53 AM
To: Jesse
Cc: MySQL List
Subject: Re: Possible Replication Issue?

Hi Jesse,

Jesse wrote:
I'm running MySQL version 5.0.22-community-nt on a Windows 2003
server.
I a
noticing A LOT of errors in there like the following:

C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Incorrect information
in file: '.\nfcamp\societies.frm'

This spans multiple databases and tables.  I am using replication, but
I
thought that I was replication only one of the databases. It could be
that
it's attempting to replicate these other databases that I don't want
replicated.  It's been a while since I set up the replication, so I
don't
remember where I need to look for this.

It sounds more like you had an ungraceful shutdown or other filesystem corruption; replication seems unlikely. Try CHECK TABLE and/or REPAIR TABLE. You may want to back up what data you still have BEFORE you run these :-) Read the relevant sections of the manual for more help.

Regards
Baron


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to