We've had very good performance with the official mysql-icc-binaries, so
I upgraded to 4.1.8 last weekend since there is no official 4.1.9 binary
on the mysql.com-site...
It didn't help with my problems, I still have replication-crashs almost
every other hour. I put a fresh snapshot from the ma
Hello.
> But I use 4.1.7, not 4.0.21 ...weird.
As said at:
http://dev.mysql.com/doc/mysql/en/news-4-1-8.html
"Fixed a bug which caused a crash when only the slave I/O thread was
stopped and started. (Bug #6148)"
I suggest you to upgrade to the latest release (4.1.9 now).
Gleb Paharenko schrieb:
Hello.
I've looked through the bug database, and the only thing
that I've found was an already-closed bug:
http://bugs.mysql.com/bug.php?id=6148
I had been looking around the Changelogs, but I had not found that one.
Sounds pretty much like my problem :(
But I use 4.1.
Hello.
I've looked through the bug database, and the only thing
that I've found was an already-closed bug:
http://bugs.mysql.com/bug.php?id=6148
Check that your server passes rpl_relayspace.test. Go to the mysql-test
directory and execute:
./mysql-test-run t/rpl_relayspace.test
Hi,
My problem still goes on... After having had the problem 2 more times
within 1 day, I decided to re-do the replication (copy the whole
database onto the slave with rsync and reset master and slave). That
only lasted for little more than 1 day and I ended up with the same error:
Could not pa
