Replication slaves quitting with binlog error

Hi all-- We have one master and 12 slaves replicating from it. Server is 4.0.16 (havn't wanted to take it down to upgrade), the slaves are 4.0.17, all running on RedHat AS. Lately, every few hours one of the machines caughs up this error, and quits replicating: Could not parse relay log event e

Re: mysql as cluster service, failover causes broken replication

Yes, the clients (appearently) read to the end of the previous file, and then sit there, while the server is writing to a new file. I was thinking this had to do with the "unclean" shutdown of MySQL-- perhapps it's something else. -Matt- > Matt Sturtz wrote: >> Hello

mysql as cluster service, failover causes broken replication

en MySQL is restarted, but the slaves keep reading from the old file, db-bin.001). The only fix seems to be CHANGE MASTER TO..., which seems somewhat error prone. Anybody else running MySQL in this type of environment have any words of wisdom? Thanks in advance for any info... -Matt Sturtz- --

Replication causes high system load

Hello, I posted about this probably a year ago or so... We run a replication slave on each of our frontend web servers (4.0.17 RPM). When a large number of updates happen on the master, it kills the performance of the web servers while getting caught up. With our application, it doesn't matter

Re: InnoDB on master, MyISAM on slaves?

Thanks for the quick reply-- > Yes, this is a common strategy, actually. Any tricks to getting the tables converted on the master without the slaves knowing about it (IE how can I do 'alter table' on the master without it being executed on the slaves)? > Transactions are not written to the binar

InnoDB on master, MyISAM on slaves?

Hello, We run a master-slave configuration and are considering migrating a few tables to InnoDB to get transaction capability... Question is, can we keep the tables as MyISAM on the slaves to maintain the high-speed accesses? I suppose this would require the SQL not being written to the bin-log

Very large table with broken index

Hello All-- We have a particularly large MyISAM table on an older MySQL (3.23.56) on an older Linux (RedHat 6.2). The table is always growing (data is never removed, except when we move it and start a new one). Yesterday one of the indexes started acting weird, so I took a look, and the .MYI fil

MySQL 4.0.15 on Red Hat Cluster

Hello, We're building a Red Hat cluster server for MySQL. Are there any gotchas, or any documentation I should read before setting up something like this? For starters, can I make MySQL believe it's proper hostname is that of the service-IP (that IP which is moved along with the service failover

Re: Replication priority / speed

bulk-loader runs? The bulk load can happen on any web server, how would it notify the others? Where would they query instead? > Can you give some more information on your master & slave config? > (hardware, OS, MySQL show variables, show status) RedHat 6.2 on i386, stock RPM install of

Re: Replication priority / speed

key efficiency is 97.35%, with an average of 1.24 q/sec (on the master-- most queries are done directly on the slave, with only updates happening on the master). We've optimized things as best we can. The problem is our customers are allowed to bulk-load keywords into our database, which c

Replication priority / speed

s in an effort to keep Apache fast... Thanks for any advice, -Matt Sturtz- - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To reque