Hi,
And fixed.
Sorry for the waste of time. Only 4 days before I was set to replace the
disk the database was on, and it is going bad. :(
-steve-
sql,query
-
Before posting, please check:
http://www.mysql.com/manual.php
Hi,
mysqlbinlog -j | mysql
works fine. I used -o instead of -j before. So I answered my last
question. When doing this:
mysqlbinlog -j | more
I see that it had advanced to the query after the one with the problem
in the trace file. In fact, the query succeeded and was there after a
REPAIR T
Quick question: Are the binlog and relaylog files the same format?
Initial tests seem to indicate that they are the same. Can I use
mysqlbinlog -o | mysql
to get the slave more up to date (without having the slave SQL thread
running)? I tried the above but the from 'show slave
status' seemed w
Below is a trace (--debug=d,enter,exit,info,error,query,general,where:
O,/tmp/mysqld.trace) of the slave thread. This is the best I can do as
far as a bug report. No other queries were running and the slave I/O
thread was idle (I firewalled its connection to the master/rest of the
world).
Without
An update. I'm now running the debug version on the slave. I could not trace
out 'info' since it wrote way too much to the trace file.
What I did find that was unique when the table crashed is this:
handle_slave_sql: query: insert into forums_posts_new_3 (
w_search: error: Got errno: 0 from
Today I added --myisam-recover=FORCE,BACKUP,QUICK
However, replication seems to not honor that setting.
I have a master that can average 7000qps and last forever, and a slave
that can only last 12 minutes at 1/10 the qps. :(
Next, I guess, is to download the debug version from MySQL and see what
