Quote:
Originally posted by Varius
Not as of yet, however I've had native mysql replication problems in the past using INNODB. I'm waiting to be able to use MySQL's new clustering software, that way I can have asynchronous replication.
In GFY's case, I assume they are doing massive inserts (every post), while tons of selects are being done on the same table, which is why I recommend trying InnoDB out.
Another option might be to run nightly optimizes on their tables if they don't already do so; I know when we had corruption problems, after having it run daily we had no more problems.
|
Yah an upgrade to 3.23.59 (replication fix in this 3 version) stoped or replication problems we used to have, since then we've upgraded had some problems on some earlier 4.0.x versions but 4.0.20 seems to be working fine.
I just didn't know if because of the way the binlogs for replication work and the differences in InnoDB and INNODB if you've seen any issue with this.
I do agree though if there are massive inserts on the same table all the selects are coming from (as we suspect) this could be a viable option.